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.

Stamp ID
STAMP-2026-1121-E2WMZZLH
Content hash
37205e0d68c549aa057b82b5aa9adf477174af57146cb2c846f7008d8dce6762
Day recorded
2026-11-22
Articles recorded that day
10
Attestation UID
0xe94bbfaeb7e225daa9b8115f2433b5851552a10a40581e1366464ddb9441e963
View on EAS
Transaction
0x942b7f3badf6087e19237811690acb4f95d007695f5f681ff32539aa16df479b
View on Basescan
Stamped
22 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 9 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
0xa79e9ee42899e8c9dc98d35501c567f03b461b2856c16e9fdc5fd24d7bbc0e09

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 before it
    0x8864d6e30de4948e3aceac329183eabae3e79369918e023bb77c19a9ff20a4e6
    0x54d1e301202aa9516b187a89187ac17fe26f465e3f26c9f955fcd09d3a478f16
  2. Step 2, combined with the value after it
    0xbbee3b261c768d4befafa966fe35d4da56d37afc7d402dcd9cb851f3b67fa3bd
    0x0aed5d9326507c9cb4cdc99242b9f25f2541017ef69bd37eca9a5ddd88ad8678
  3. Step 3, combined with the value before it
    0x68318502f0ca5111ed9be07aa84b109f6cacc2bd6f267a556595170f770a49c3
    0x8c1c4d67744b0150fcbf572896bb87bb6460376b7e151d6ee0010f22e348509e
  4. Step 4, combined with the value after it
    0x447207169abf781ec940d5176bce7fb9a72d703aa8509ccab2808404fa7c76db
    0x82e394dafb9a5a12fccd49e83d5accf43720bcd7b1695442fe0836b62aa6f71d

    This is the value for the whole day.

Value these steps arrive at
0x82e394dafb9a5a12fccd49e83d5accf43720bcd7b1695442fe0836b62aa6f71d

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
0x82e394dafb9a5a12fccd49e83d5accf43720bcd7b1695442fe0836b62aa6f71d
Read from Base
0x82e394dafb9a5a12fccd49e83d5accf43720bcd7b1695442fe0836b62aa6f71d
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":"poweredbyplants","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Looking for a fresh and filling breakfast? Try avocado toast topped with sautée…

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-1121-E2WMZZLH/canonical" | shasum -a 256

    Should print 37205e0d68c549aa057b82b5aa9adf477174af57146cb2c846f7008d8dce6762

  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-1121-E2WMZZLH CONTENT=37205e0d68c549aa057b82b5aa9adf477174af57146cb2c846f7008d8dce6762 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print a79e9ee42899e8c9dc98d35501c567f03b461b2856c16e9fdc5fd24d7bbc0e09

  3. 3. Combine step 1

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

    printf '01%s%s' "8864d6e30de4948e3aceac329183eabae3e79369918e023bb77c19a9ff20a4e6" "a79e9ee42899e8c9dc98d35501c567f03b461b2856c16e9fdc5fd24d7bbc0e09" | xxd -r -p | shasum -a 256

    Should print 54d1e301202aa9516b187a89187ac17fe26f465e3f26c9f955fcd09d3a478f16

  4. 4. Combine step 2

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

    printf '01%s%s' "54d1e301202aa9516b187a89187ac17fe26f465e3f26c9f955fcd09d3a478f16" "bbee3b261c768d4befafa966fe35d4da56d37afc7d402dcd9cb851f3b67fa3bd" | xxd -r -p | shasum -a 256

    Should print 0aed5d9326507c9cb4cdc99242b9f25f2541017ef69bd37eca9a5ddd88ad8678

  5. 5. Combine step 3

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

    printf '01%s%s' "68318502f0ca5111ed9be07aa84b109f6cacc2bd6f267a556595170f770a49c3" "0aed5d9326507c9cb4cdc99242b9f25f2541017ef69bd37eca9a5ddd88ad8678" | xxd -r -p | shasum -a 256

    Should print 8c1c4d67744b0150fcbf572896bb87bb6460376b7e151d6ee0010f22e348509e

  6. 6. Combine step 4

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

    printf '01%s%s' "8c1c4d67744b0150fcbf572896bb87bb6460376b7e151d6ee0010f22e348509e" "447207169abf781ec940d5176bce7fb9a72d703aa8509ccab2808404fa7c76db" | xxd -r -p | shasum -a 256

    Should print 82e394dafb9a5a12fccd49e83d5accf43720bcd7b1695442fe0836b62aa6f71d

  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/0xe94bbfaeb7e225daa9b8115f2433b5851552a10a40581e1366464ddb9441e963

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

Read the specification