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-0915-W6KBDDZO
Content hash
a2d41bedd8657963f239abd6ea5e3fb0f577e53dbb3e4afe9af7e17909b78128
Day recorded
2026-09-16
Articles recorded that day
11
Attestation UID
0x54e8c20577bfacf8072eb87b36b1bfa02b4db37247336a2c44ccaa82df5ef5c2
View on EAS
Transaction
0x27483e4138b3cb63387441033318cbcfa64c52adb28abf76257ce8b5aa03ef19
View on Basescan
Stamped
17 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 10 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
0x504204479227241123475b67f3fb4e0b1541703f42b2c59e47032e4e8b5f7722

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
    0xf151423791f771eb1ee5201eb5ccbe577eadc466d20af016255b8faa026d6c08
    0x1d989834b8772060be9d6261ba87399f0445016145123fd3428347f2dd9493dd
  2. Step 2, combined with the value after it
    0x10f8cd26c74c8b7012fd1213d92600f34d833c311f90ab354402d0399eb5fe87
    0x2833408ec18f99b6743e4b1d92b1b4bbc4d9bfa009fe72217f3ffe85845091d8
  3. Step 3, combined with the value before it
    0x45b6a0f20f993e761d8aead43f3695dbd2bccd21f8b01cb82137ebd8b84b7f6c
    0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

    This is the value for the whole day.

Value these steps arrive at
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

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
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50
Read from Base
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50
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-0915-W6KBDDZO/canonical" | shasum -a 256

    Should print a2d41bedd8657963f239abd6ea5e3fb0f577e53dbb3e4afe9af7e17909b78128

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

    Should print 504204479227241123475b67f3fb4e0b1541703f42b2c59e47032e4e8b5f7722

  3. 3. Combine step 1

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

    printf '01%s%s' "f151423791f771eb1ee5201eb5ccbe577eadc466d20af016255b8faa026d6c08" "504204479227241123475b67f3fb4e0b1541703f42b2c59e47032e4e8b5f7722" | xxd -r -p | shasum -a 256

    Should print 1d989834b8772060be9d6261ba87399f0445016145123fd3428347f2dd9493dd

  4. 4. Combine step 2

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

    printf '01%s%s' "1d989834b8772060be9d6261ba87399f0445016145123fd3428347f2dd9493dd" "10f8cd26c74c8b7012fd1213d92600f34d833c311f90ab354402d0399eb5fe87" | xxd -r -p | shasum -a 256

    Should print 2833408ec18f99b6743e4b1d92b1b4bbc4d9bfa009fe72217f3ffe85845091d8

  5. 5. Combine step 3

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

    printf '01%s%s' "45b6a0f20f993e761d8aead43f3695dbd2bccd21f8b01cb82137ebd8b84b7f6c" "2833408ec18f99b6743e4b1d92b1b4bbc4d9bfa009fe72217f3ffe85845091d8" | xxd -r -p | shasum -a 256

    Should print 7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

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

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

Read the specification