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-0917-RX6IMCOZ
Content hash
8a91a3903ffbfdf9aef5aed7448033a46e179e3506fb9abd0e8aed7ea8db0e89
Day recorded
2026-09-18
Articles recorded that day
13
Attestation UID
0x99cf5acde28f98446b07d9f381ccf6b9dc4ff37ce0871d10b54a80bdb98095de
View on EAS
Transaction
0x61ee343cde25983c3ac3ae4c39e621400f411eefee4b607c85dfd170f3bd4190
View on Basescan
Stamped
19 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 12 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
0x0afbb127a8e817efa3f5acb3f0a27cfdc12f5002f073e656f4a4b8a1fa0d310d

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
    0x1f8acc713ee14e26e1f8ea589b3de5a696327979e251ffbcf3abe41e06859278
    0x9a5d41fdff2a5ef08c052a047b3b0d00f21b46a1615f63894d73bc8f0132edba
  2. Step 2, combined with the value before it
    0x84c25a24cd93950b48eca587b12e1cd1b3aeebcd25eb312ab03170f75800c145
    0x0252621b0246461f9699c1e304bdf0b1a0cb448a7f37ea1a550e00a3ca2d5f23
  3. Step 3, combined with the value before it
    0x313a6fe993c1def9e9a8f850f3aa4044606c2aa7bd577952abac571c777524a9
    0x2179430ea0588befc303ccd6515f5da08e40ad99c24504fce746072a194ebe90
  4. Step 4, combined with the value after it
    0xa66ce1f1da049ece5c77c50b28daa4731b6ca2a516b6ac8e5a1ecc6941ecd1dc
    0x31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51

    This is the value for the whole day.

Value these steps arrive at
0x31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51

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
0x31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51
Read from Base
0x31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51
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":"PositiveVibez","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"You can’t always control what happens around you, but you can choose how you resp…

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-0917-RX6IMCOZ/canonical" | shasum -a 256

    Should print 8a91a3903ffbfdf9aef5aed7448033a46e179e3506fb9abd0e8aed7ea8db0e89

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

    Should print 0afbb127a8e817efa3f5acb3f0a27cfdc12f5002f073e656f4a4b8a1fa0d310d

  3. 3. Combine step 1

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

    printf '01%s%s' "1f8acc713ee14e26e1f8ea589b3de5a696327979e251ffbcf3abe41e06859278" "0afbb127a8e817efa3f5acb3f0a27cfdc12f5002f073e656f4a4b8a1fa0d310d" | xxd -r -p | shasum -a 256

    Should print 9a5d41fdff2a5ef08c052a047b3b0d00f21b46a1615f63894d73bc8f0132edba

  4. 4. Combine step 2

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

    printf '01%s%s' "84c25a24cd93950b48eca587b12e1cd1b3aeebcd25eb312ab03170f75800c145" "9a5d41fdff2a5ef08c052a047b3b0d00f21b46a1615f63894d73bc8f0132edba" | xxd -r -p | shasum -a 256

    Should print 0252621b0246461f9699c1e304bdf0b1a0cb448a7f37ea1a550e00a3ca2d5f23

  5. 5. Combine step 3

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

    printf '01%s%s' "313a6fe993c1def9e9a8f850f3aa4044606c2aa7bd577952abac571c777524a9" "0252621b0246461f9699c1e304bdf0b1a0cb448a7f37ea1a550e00a3ca2d5f23" | xxd -r -p | shasum -a 256

    Should print 2179430ea0588befc303ccd6515f5da08e40ad99c24504fce746072a194ebe90

  6. 6. Combine step 4

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

    printf '01%s%s' "2179430ea0588befc303ccd6515f5da08e40ad99c24504fce746072a194ebe90" "a66ce1f1da049ece5c77c50b28daa4731b6ca2a516b6ac8e5a1ecc6941ecd1dc" | xxd -r -p | shasum -a 256

    Should print 31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51

  7. 7. 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/0x99cf5acde28f98446b07d9f381ccf6b9dc4ff37ce0871d10b54a80bdb98095de

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

Read the specification