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.

Vegan Dessert Recipe: Carrot Cake!

@poweredbyplants · 4 Oct 2026

Stamp ID
STAMP-2026-1004-3NZOY6M7
Content hash
12e27839c7356f69e13f646ab58d786ad349f64cd4f2c2ea6d28a17af4b46634
Day recorded
2026-10-05
Articles recorded that day
14
Attestation UID
0x99cd6b1d642d6f453cbd531cf2d5c5dee53a3ac0f82ed61ff6b666d95537f3be
View on EAS
Transaction
0x479b7310c703e960a819dd574d78be722e75921ba6309910ae4511a65681eef2
View on Basescan
Stamped
6 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0xe63c598b92a71a59910ea16f94598346b40c454601b47d13f1af9ce08131f16e

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
    0xeff3fbee512a183f4cb3d2a953e94c24f83d5635b48bedf162fd1f88006f8a0f
    0xd802545b583a2c7cd1a5c687a0a3a265857e98a23c13c310b7395b1283a47c3c
  2. Step 2, combined with the value after it
    0x2aad3d43b5cd68fd309f445544ee8d2935a4be4ef2862a6f44be417e4ab62c9c
    0xef0e364c3bec81306843282338faec7e03a988ff384e24c70f628dcb319db925
  3. Step 3, combined with the value after it
    0xae88aafe666bca1ec42c2b36612221a4979596811c1d34b76123a88c61312a5d
    0x56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58
  4. Step 4, combined with the value after it
    0x99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb
    0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

    This is the value for the whole day.

Value these steps arrive at
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

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
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1
Read from Base
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1
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":"Moist, warmly spiced, and packed with freshly grated carrots, this Vegan Carrot…

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-1004-3NZOY6M7/canonical" | shasum -a 256

    Should print 12e27839c7356f69e13f646ab58d786ad349f64cd4f2c2ea6d28a17af4b46634

  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-1004-3NZOY6M7 CONTENT=12e27839c7356f69e13f646ab58d786ad349f64cd4f2c2ea6d28a17af4b46634 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print e63c598b92a71a59910ea16f94598346b40c454601b47d13f1af9ce08131f16e

  3. 3. Combine step 1

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

    printf '01%s%s' "e63c598b92a71a59910ea16f94598346b40c454601b47d13f1af9ce08131f16e" "eff3fbee512a183f4cb3d2a953e94c24f83d5635b48bedf162fd1f88006f8a0f" | xxd -r -p | shasum -a 256

    Should print d802545b583a2c7cd1a5c687a0a3a265857e98a23c13c310b7395b1283a47c3c

  4. 4. Combine step 2

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

    printf '01%s%s' "d802545b583a2c7cd1a5c687a0a3a265857e98a23c13c310b7395b1283a47c3c" "2aad3d43b5cd68fd309f445544ee8d2935a4be4ef2862a6f44be417e4ab62c9c" | xxd -r -p | shasum -a 256

    Should print ef0e364c3bec81306843282338faec7e03a988ff384e24c70f628dcb319db925

  5. 5. Combine step 3

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

    printf '01%s%s' "ef0e364c3bec81306843282338faec7e03a988ff384e24c70f628dcb319db925" "ae88aafe666bca1ec42c2b36612221a4979596811c1d34b76123a88c61312a5d" | xxd -r -p | shasum -a 256

    Should print 56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58

  6. 6. Combine step 4

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

    printf '01%s%s' "56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58" "99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb" | xxd -r -p | shasum -a 256

    Should print 11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

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

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

Read the specification