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.

Creamy, Delicious & Completely Vegan

@poweredbyplants · 25 Sept 2026

Stamp ID
STAMP-2026-0925-PTYN3WPS
Content hash
4ecfa3f419c3e922c843a50491938ccf31557a65bc68fcfc0dae207d4c0112d0
Day recorded
2026-09-26
Articles recorded that day
20
Attestation UID
0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44
View on EAS
Transaction
0x8773b62d3c7fe3c39180795fdbf303e39a988305339fd36d0f85017972c0bcd5
View on Basescan
Stamped
26 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 19 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
0x57f3447e7203197c9d662e3337c4f4aa1e284fd3f41ea242be86cbc40b080096

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
    0x77c3d2e0b91db37c74d72ec846bf29a630e63e405ba57ba6fa0ae40011bcff88
    0xfef56e317e718b39b5414d784eb6ed463d1c19f59a9f465ba6f82bf63923cced
  2. Step 2, combined with the value before it
    0x20d828c765365bbaa4d4dd0af4b59b3b6ff62c1bc63803ff59c020785b821167
    0x8c5e0bcdad701cf810b7c1d35001164268482c86a64c1e579bccb96aafd48ee4
  3. Step 3, combined with the value before it
    0x1c5adf9f24c1361259bd3f75f752da821657b46f72772b585ff2cbfc77870e91
    0xeef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba
  4. Step 4, combined with the value before it
    0x97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb
    0xc1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c
  5. Step 5, combined with the value after it
    0x338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f
    0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

    This is the value for the whole day.

Value these steps arrive at
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

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
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
Read from Base
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
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 dairy-free spread that actually tastes indulgent? Tofu cream chee…

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-0925-PTYN3WPS/canonical" | shasum -a 256

    Should print 4ecfa3f419c3e922c843a50491938ccf31557a65bc68fcfc0dae207d4c0112d0

  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-0925-PTYN3WPS CONTENT=4ecfa3f419c3e922c843a50491938ccf31557a65bc68fcfc0dae207d4c0112d0 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 57f3447e7203197c9d662e3337c4f4aa1e284fd3f41ea242be86cbc40b080096

  3. 3. Combine step 1

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

    printf '01%s%s' "77c3d2e0b91db37c74d72ec846bf29a630e63e405ba57ba6fa0ae40011bcff88" "57f3447e7203197c9d662e3337c4f4aa1e284fd3f41ea242be86cbc40b080096" | xxd -r -p | shasum -a 256

    Should print fef56e317e718b39b5414d784eb6ed463d1c19f59a9f465ba6f82bf63923cced

  4. 4. Combine step 2

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

    printf '01%s%s' "20d828c765365bbaa4d4dd0af4b59b3b6ff62c1bc63803ff59c020785b821167" "fef56e317e718b39b5414d784eb6ed463d1c19f59a9f465ba6f82bf63923cced" | xxd -r -p | shasum -a 256

    Should print 8c5e0bcdad701cf810b7c1d35001164268482c86a64c1e579bccb96aafd48ee4

  5. 5. Combine step 3

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

    printf '01%s%s' "1c5adf9f24c1361259bd3f75f752da821657b46f72772b585ff2cbfc77870e91" "8c5e0bcdad701cf810b7c1d35001164268482c86a64c1e579bccb96aafd48ee4" | xxd -r -p | shasum -a 256

    Should print eef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba

  6. 6. Combine step 4

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

    printf '01%s%s' "97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb" "eef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba" | xxd -r -p | shasum -a 256

    Should print c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c

  7. 7. Combine step 5

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

    printf '01%s%s' "c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c" "338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f" | xxd -r -p | shasum -a 256

    Should print 8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

  8. 8. 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/0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44

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

Read the specification