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.

Stamp ID
STAMP-2026-0910-FYY7MAEB
Content hash
cee0cabf6dd220d7859592b9f690d8f568db339e83bd939a5de006860119edf9
Day recorded
2026-09-11
Articles recorded that day
7
Attestation UID
0x43dd040a36ca280cd09cc8ecc6139eac09edbe31e9fc66b954bcb354e6632ac8
View on EAS
Transaction
0x3bcb5ee308c0e96aeb2462c554339d1f273ddc4af14e018f66d66740b22a0dd6
View on Basescan
Stamped
11 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 6 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
0x21b0063de46d83a9783b314c0f2e36e3d24fd88763f594534410f876e14eeb3c

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
    0x4fb0002b31cc319008c11a156a3037662aabf4aa38225eb210b2f5aafa0677ca
    0x9ce4219c6e9f73e60d8404aecc9b4f75bc3bb53ecdc134253dee75c5b28c8958
  2. Step 2, combined with the value after it
    0xd3c9887a7bb069ef5742cb5389769b1ae4774cb750a229af8ab60ce11b7c9b4d
    0x5e650b8006d2a7eda81bb5d4ed9c0d4d00a341c3830745859eaba27f43433dfa
  3. Step 3, combined with the value after it
    0x9d219722d7b5ca1b6b93640cb99cb26872d115b20f8fb163e9367b343dff4564
    0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

    This is the value for the whole day.

Value these steps arrive at
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

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
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7
Read from Base
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7
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.

The exact text is not available for this article right now. The command below still reaches it.

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-0910-FYY7MAEB/canonical" | shasum -a 256

    Should print cee0cabf6dd220d7859592b9f690d8f568db339e83bd939a5de006860119edf9

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

    Should print 21b0063de46d83a9783b314c0f2e36e3d24fd88763f594534410f876e14eeb3c

  3. 3. Combine step 1

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

    printf '01%s%s' "4fb0002b31cc319008c11a156a3037662aabf4aa38225eb210b2f5aafa0677ca" "21b0063de46d83a9783b314c0f2e36e3d24fd88763f594534410f876e14eeb3c" | xxd -r -p | shasum -a 256

    Should print 9ce4219c6e9f73e60d8404aecc9b4f75bc3bb53ecdc134253dee75c5b28c8958

  4. 4. Combine step 2

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

    printf '01%s%s' "9ce4219c6e9f73e60d8404aecc9b4f75bc3bb53ecdc134253dee75c5b28c8958" "d3c9887a7bb069ef5742cb5389769b1ae4774cb750a229af8ab60ce11b7c9b4d" | xxd -r -p | shasum -a 256

    Should print 5e650b8006d2a7eda81bb5d4ed9c0d4d00a341c3830745859eaba27f43433dfa

  5. 5. Combine step 3

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

    printf '01%s%s' "5e650b8006d2a7eda81bb5d4ed9c0d4d00a341c3830745859eaba27f43433dfa" "9d219722d7b5ca1b6b93640cb99cb26872d115b20f8fb163e9367b343dff4564" | xxd -r -p | shasum -a 256

    Should print 23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

  6. 6. 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/0x43dd040a36ca280cd09cc8ecc6139eac09edbe31e9fc66b954bcb354e6632ac8

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

Read the specification