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-1120-E3TZWU6G
Content hash
208c61015cde373edc3bc24759325239bad5ca9e54d95224f6fbd7751e9960a1
Day recorded
2026-11-21
Articles recorded that day
18
Attestation UID
0x6dbc8bcb58dbb79501c2036313639713eb87cb0e96a5fec5d753c561013dad57
View on EAS
Transaction
0xa058217606bfc18a974c2bc8e10bea173b08ca8cfc08b8e8f3edf199e5341003
View on Basescan
Stamped
21 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 17 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
0x340001d72edd6a3e9edcc03a93b7e2a894ff2616d2b47ee90c1a153099896914

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
    0x483c2bb2897b7f1a65542a1ccf1931b71acfa6d5f766332293827dcca3d73499
    0x2abf069b1d76444042fdcef7059c8aadb7c0283051caa2452c152510764f78d0
  2. Step 2, combined with the value before it
    0xece598f63e9d8ea43ddb1e42fe5be00c7cff1f038c7bfa82861f34388d35599d
    0x533dee1cc793ea072177a4702ec7bdeaab9b37a4599284006a294b561c431fa6
  3. Step 3, combined with the value after it
    0x86213ba8fbf4f40c8082af12a953cb8bdee57a025b65ebaaddf8e2a1f328a1b0
    0x397cc53c6d9f606f7e7856498d873f80a7ab4501390d4d97691b6517c236a82e
  4. Step 4, combined with the value after it
    0x91702c4a1595bafe1e1136925bd3622e41c4533acd0124cab397325813880c3b
    0x6569cf5af2f54622e6373cc891f0d427dc62f02d22628fafe3658631cc666335
  5. Step 5, combined with the value after it
    0xa3df4ccbde9be8aebc4c2009f23c8a9c15cac70ae77cd2ad8470542b099e2c9d
    0xb6d3f41aee45cdce26af20400ccffcd67856ab1e5c6133bfa98242d913a785b1

    This is the value for the whole day.

Value these steps arrive at
0xb6d3f41aee45cdce26af20400ccffcd67856ab1e5c6133bfa98242d913a785b1

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
0xb6d3f41aee45cdce26af20400ccffcd67856ab1e5c6133bfa98242d913a785b1
Read from Base
0xb6d3f41aee45cdce26af20400ccffcd67856ab1e5c6133bfa98242d913a785b1
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":"simple_recipes_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Craving something sweet and chocolatey? This simple homemade chocolate mou…

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-1120-E3TZWU6G/canonical" | shasum -a 256

    Should print 208c61015cde373edc3bc24759325239bad5ca9e54d95224f6fbd7751e9960a1

  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-1120-E3TZWU6G CONTENT=208c61015cde373edc3bc24759325239bad5ca9e54d95224f6fbd7751e9960a1 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 340001d72edd6a3e9edcc03a93b7e2a894ff2616d2b47ee90c1a153099896914

  3. 3. Combine step 1

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

    printf '01%s%s' "483c2bb2897b7f1a65542a1ccf1931b71acfa6d5f766332293827dcca3d73499" "340001d72edd6a3e9edcc03a93b7e2a894ff2616d2b47ee90c1a153099896914" | xxd -r -p | shasum -a 256

    Should print 2abf069b1d76444042fdcef7059c8aadb7c0283051caa2452c152510764f78d0

  4. 4. Combine step 2

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

    printf '01%s%s' "ece598f63e9d8ea43ddb1e42fe5be00c7cff1f038c7bfa82861f34388d35599d" "2abf069b1d76444042fdcef7059c8aadb7c0283051caa2452c152510764f78d0" | xxd -r -p | shasum -a 256

    Should print 533dee1cc793ea072177a4702ec7bdeaab9b37a4599284006a294b561c431fa6

  5. 5. Combine step 3

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

    printf '01%s%s' "533dee1cc793ea072177a4702ec7bdeaab9b37a4599284006a294b561c431fa6" "86213ba8fbf4f40c8082af12a953cb8bdee57a025b65ebaaddf8e2a1f328a1b0" | xxd -r -p | shasum -a 256

    Should print 397cc53c6d9f606f7e7856498d873f80a7ab4501390d4d97691b6517c236a82e

  6. 6. Combine step 4

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

    printf '01%s%s' "397cc53c6d9f606f7e7856498d873f80a7ab4501390d4d97691b6517c236a82e" "91702c4a1595bafe1e1136925bd3622e41c4533acd0124cab397325813880c3b" | xxd -r -p | shasum -a 256

    Should print 6569cf5af2f54622e6373cc891f0d427dc62f02d22628fafe3658631cc666335

  7. 7. Combine step 5

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

    printf '01%s%s' "6569cf5af2f54622e6373cc891f0d427dc62f02d22628fafe3658631cc666335" "a3df4ccbde9be8aebc4c2009f23c8a9c15cac70ae77cd2ad8470542b099e2c9d" | xxd -r -p | shasum -a 256

    Should print b6d3f41aee45cdce26af20400ccffcd67856ab1e5c6133bfa98242d913a785b1

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

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

Read the specification