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-0908-LZQMMIQ2
Content hash
e8250549329ea2d68f63f2115605e57f96ee40f62ca31271e7e6b4430332bc39
Day recorded
2026-09-09
Articles recorded that day
5
Attestation UID
0x041787fece6c3c97abcdbdfd65d43fd8125061a1f4e92a7f5c47448ecdc8af04
View on EAS
Transaction
0xd71488576af19f7a6acb3cc7cb24389b2387be4a2954deaab8ebbf837587d546
View on Basescan
Stamped
9 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 4 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
0x28bf295a57968b277a9e13fcdb7e526df2809e9cd449ba8e1230b90acf715570

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
    0xaae9b9c1165a65a4ef46acb6bef5185201c5b5c1071f1363e0edbdd3c4d97ad0
    0xc06d3d56f4fff8ede166ce30e481a37cd1599bced0921dec2ba234be914bba86
  2. Step 2, combined with the value after it
    0x8a9e14acf6fe0c47f83b59044352044477b85f139fb9df4efb8df3166759691d
    0xc0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07
  3. Step 3, combined with the value after it
    0x1b30e5f2d6a413c35cae4be57ffcb0f83ac838f84cc8e682af6a227dfeace9a9
    0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

    This is the value for the whole day.

Value these steps arrive at
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

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
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789
Read from Base
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789
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-0908-LZQMMIQ2/canonical" | shasum -a 256

    Should print e8250549329ea2d68f63f2115605e57f96ee40f62ca31271e7e6b4430332bc39

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

    Should print 28bf295a57968b277a9e13fcdb7e526df2809e9cd449ba8e1230b90acf715570

  3. 3. Combine step 1

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

    printf '01%s%s' "28bf295a57968b277a9e13fcdb7e526df2809e9cd449ba8e1230b90acf715570" "aae9b9c1165a65a4ef46acb6bef5185201c5b5c1071f1363e0edbdd3c4d97ad0" | xxd -r -p | shasum -a 256

    Should print c06d3d56f4fff8ede166ce30e481a37cd1599bced0921dec2ba234be914bba86

  4. 4. Combine step 2

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

    printf '01%s%s' "c06d3d56f4fff8ede166ce30e481a37cd1599bced0921dec2ba234be914bba86" "8a9e14acf6fe0c47f83b59044352044477b85f139fb9df4efb8df3166759691d" | xxd -r -p | shasum -a 256

    Should print c0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07

  5. 5. Combine step 3

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

    printf '01%s%s' "c0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07" "1b30e5f2d6a413c35cae4be57ffcb0f83ac838f84cc8e682af6a227dfeace9a9" | xxd -r -p | shasum -a 256

    Should print 23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

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

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

Read the specification