Verify

Verified on Base

This article has not changed since Vitahash recorded it on the Base blockchain. Everything below can be checked without taking our word for any of it.

Skip the Smoke, Protect Your Glow

@glowguide_daily · 19 Oct 2026

Stamp ID
STAMP-2026-1019-OQGPLCI7
Content hash
fcaec12418520d0262378f2b8c9aa568651da798062c0c40ce6943eddf662b04
Day recorded
2026-10-20
Articles recorded that day
16
Attestation UID
0x93d64f817aa96872c3a5248b96e9c91608399a50c8c4273adfbf62f971f167ec
View on EAS
Transaction
0x9fe633b4d4a34f5e6242b3cf0ff45c83ab4a7ecc11a1084cc69f42989b8ac574
View on Basescan
Stamped
20 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 15 articles published that day, one step at a time, until the whole day became a single value. That one value is what Vitahash wrote to the blockchain. Change a single character of this article and the starting value below changes, so none of the steps would land on the recorded one.

Starting value for this article
0x26498e45c75dffa9ee19647366a50372f43761d7d0e0196809b158b7da55ef40

Built from this article's content hash and its stamp ID, as sha256(0x00 || sha256(utf8(stampId)) || contentHash).

  1. Step 1, combined with the value after it
    0x9056eeee4e93e6db38693fb751e0964c2a3f7cf3ae46f91e8a68b4ac648ff31a
    0x0b7727c35cf459cfc5752e49775c0e034194278411cd2c4a80cf87468eb653db
  2. Step 2, combined with the value after it
    0xe5a7f9be5e8a0fb387e602eedf4621aea794e6113fbaee69993e321ec036bdc5
    0x1b1d6b5965ba3f053b565702de105e1a846917dc966ade12819956414699c508
  3. Step 3, combined with the value after it
    0xf3be809cdf5733ebea51ecabf9ecf4d61367fe96551c26a144de6d12d32654ab
    0x2ec43559cf0e122de80e61aaaf34716e108cca54701d2013b438a0a9f93c5af5
  4. Step 4, combined with the value before it
    0x6200cf6d055554851ed81c34e9916b3887bc3f64e1abeda6bd3f37592300c9a2
    0x9022c784ca2a1d3863d7e5472e41a5d2867f0f68e6e21431763247963c30caef

    This is the value for the whole day.

Value these steps arrive at
0x9022c784ca2a1d3863d7e5472e41a5d2867f0f68e6e21431763247963c30caef

What the blockchain says

Two values, reached two different ways. The one above was worked out from this article. The one below was read back from the record on Base.

Worked out from this article
0x9022c784ca2a1d3863d7e5472e41a5d2867f0f68e6e21431763247963c30caef
Read from Base
0x9022c784ca2a1d3863d7e5472e41a5d2867f0f68e6e21431763247963c30caef
Read it yourself on EAS

They are the same value, so this article was published that day with exactly the text above.

Check it yourself

Every number on this page came from Vitahash. Copy the article's exact text below and check it against the hash above, using any SHA-256 tool.

{"abstract":null,"agreement":false,"authors":[{"identity":"glowguide_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Want healthier, glowing skin? Skip the smoke. Smoking can break down collagen a…

Copy this text, paste it into any SHA-256 tool, and compare the result with the hash shown above. If the two match, this is exactly what Vitahash recorded.

For a technical reader: the terminal route

  1. 1. Hash the article yourself

    This downloads the exact text Vitahash hashed, in the exact form it hashed it, and hashes it again on your machine. Nothing Vitahash wrote runs here.

    curl -s "https://api.vitahash.org/api/verify/STAMP-2026-1019-OQGPLCI7/canonical" | shasum -a 256

    Should print fcaec12418520d0262378f2b8c9aa568651da798062c0c40ce6943eddf662b04

  2. 2. Build this article's starting value

    The stamp ID is folded in with the hash, so one article's record can never stand in for another's.

    STAMP=STAMP-2026-1019-OQGPLCI7 CONTENT=fcaec12418520d0262378f2b8c9aa568651da798062c0c40ce6943eddf662b04 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 26498e45c75dffa9ee19647366a50372f43761d7d0e0196809b158b7da55ef40

  3. 3. Combine step 1

    The value you have goes first, then the published value.

    printf '01%s%s' "26498e45c75dffa9ee19647366a50372f43761d7d0e0196809b158b7da55ef40" "9056eeee4e93e6db38693fb751e0964c2a3f7cf3ae46f91e8a68b4ac648ff31a" | xxd -r -p | shasum -a 256

    Should print 0b7727c35cf459cfc5752e49775c0e034194278411cd2c4a80cf87468eb653db

  4. 4. Combine step 2

    The value you have goes first, then the published value.

    printf '01%s%s' "0b7727c35cf459cfc5752e49775c0e034194278411cd2c4a80cf87468eb653db" "e5a7f9be5e8a0fb387e602eedf4621aea794e6113fbaee69993e321ec036bdc5" | xxd -r -p | shasum -a 256

    Should print 1b1d6b5965ba3f053b565702de105e1a846917dc966ade12819956414699c508

  5. 5. Combine step 3

    The value you have goes first, then the published value.

    printf '01%s%s' "1b1d6b5965ba3f053b565702de105e1a846917dc966ade12819956414699c508" "f3be809cdf5733ebea51ecabf9ecf4d61367fe96551c26a144de6d12d32654ab" | xxd -r -p | shasum -a 256

    Should print 2ec43559cf0e122de80e61aaaf34716e108cca54701d2013b438a0a9f93c5af5

  6. 6. Combine step 4

    The published value goes first, then the value you have.

    printf '01%s%s' "6200cf6d055554851ed81c34e9916b3887bc3f64e1abeda6bd3f37592300c9a2" "2ec43559cf0e122de80e61aaaf34716e108cca54701d2013b438a0a9f93c5af5" | xxd -r -p | shasum -a 256

    Should print 9022c784ca2a1d3863d7e5472e41a5d2867f0f68e6e21431763247963c30caef

  7. 7. Compare with the blockchain

    The last value above is what the whole day came to. Read the record on Base and check its merkleRoot field is the same. Vitahash is not involved in this step at all.

    https://base.easscan.org/attestation/view/0x93d64f817aa96872c3a5248b96e9c91608399a50c8c4273adfbf62f971f167ec

The rules these commands follow are written down in full, so anyone can reimplement them.

Read the specification