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-0922-VWABEZQS
Content hash
a0beea5c7f19970f531b93540a5848111576725859f6ff6df458065f149951d4
Day recorded
2026-09-23
Articles recorded that day
19
Attestation UID
0x312f5bdaee9c1cd4c9c9e451ce2d932f82aa65985854eb05f9075f80314e1b63
View on EAS
Transaction
0x54b4b79e498e2ec45d4be92b4c1c5b8f94b2c646cefaf982166895ba22ef85c1
View on Basescan
Stamped
23 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0xc04faf615c4c6c10add2fd038c8ce563bdffe486c34a1ac5ef8e9f97695c1de8

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
    0xc217184c1d8fa31b2a4ce7bf37e0f404a70088e9f24b6409b5c6df6b2d56bf1b
    0x20b6285b23b240b71dcdfb05b7ad895a2fb92847fa7b62369d5e6a66d304069e
  2. Step 2, combined with the value after it
    0x935a62a025f366a1addb3e96254201410ee53edc1d55190c0283a0dd52a5a0f1
    0x7a88f62292afb2658d20a5063a2b18d13343fa8e26ae33cb4daa3b0a0c688944
  3. Step 3, combined with the value before it
    0xe63d808641c9100111b6b6585a9ed386e34c5f36ce79c50f14b6aaf0618b12fe
    0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d

    This is the value for the whole day.

Value these steps arrive at
0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d

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
0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d
Read from Base
0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d
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-0922-VWABEZQS/canonical" | shasum -a 256

    Should print a0beea5c7f19970f531b93540a5848111576725859f6ff6df458065f149951d4

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

    Should print c04faf615c4c6c10add2fd038c8ce563bdffe486c34a1ac5ef8e9f97695c1de8

  3. 3. Combine step 1

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

    printf '01%s%s' "c04faf615c4c6c10add2fd038c8ce563bdffe486c34a1ac5ef8e9f97695c1de8" "c217184c1d8fa31b2a4ce7bf37e0f404a70088e9f24b6409b5c6df6b2d56bf1b" | xxd -r -p | shasum -a 256

    Should print 20b6285b23b240b71dcdfb05b7ad895a2fb92847fa7b62369d5e6a66d304069e

  4. 4. Combine step 2

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

    printf '01%s%s' "20b6285b23b240b71dcdfb05b7ad895a2fb92847fa7b62369d5e6a66d304069e" "935a62a025f366a1addb3e96254201410ee53edc1d55190c0283a0dd52a5a0f1" | xxd -r -p | shasum -a 256

    Should print 7a88f62292afb2658d20a5063a2b18d13343fa8e26ae33cb4daa3b0a0c688944

  5. 5. Combine step 3

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

    printf '01%s%s' "e63d808641c9100111b6b6585a9ed386e34c5f36ce79c50f14b6aaf0618b12fe" "7a88f62292afb2658d20a5063a2b18d13343fa8e26ae33cb4daa3b0a0c688944" | xxd -r -p | shasum -a 256

    Should print 08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d

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

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

Read the specification