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.

🎮 Ritual of Raven

Cozy Game Diary · 26 Sept 2026

Stamp ID
STAMP-2026-0926-DLSA5WPT
Content hash
2b11803968ebc5978872e4ce8bf81e109a43d012c0016a287b44e22147555b02
Day recorded
2026-09-26
Articles recorded that day
20
Attestation UID
0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44
View on EAS
Transaction
0x8773b62d3c7fe3c39180795fdbf303e39a988305339fd36d0f85017972c0bcd5
View on Basescan
Stamped
26 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 19 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
0xa19fd2ff9d3845fdb3beffd1ea601bf329b53527d0ad8e5ecac93953f3b63637

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
    0xeb55d3aec05c54016d370940764eca0d0477bac746b42cae57a927dc39692f1c
    0x575aa995fa93b290cd04afd25a3ff70f5034e864bc7b21aa79c1f042031b5fef
  2. Step 2, combined with the value before it
    0xde5d72e6facc516b521a9dcc7f7d35c21eac5292319837957ba97c08d6e19a17
    0x338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f
  3. Step 3, combined with the value before it
    0xc1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c
    0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

    This is the value for the whole day.

Value these steps arrive at
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

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
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
Read from Base
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
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":"harvesthealth","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Looking for a cozy game for Friday night? 🐦‍⬛✨","type":"text"}],"type":"paragraph…

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-0926-DLSA5WPT/canonical" | shasum -a 256

    Should print 2b11803968ebc5978872e4ce8bf81e109a43d012c0016a287b44e22147555b02

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

    Should print a19fd2ff9d3845fdb3beffd1ea601bf329b53527d0ad8e5ecac93953f3b63637

  3. 3. Combine step 1

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

    printf '01%s%s' "eb55d3aec05c54016d370940764eca0d0477bac746b42cae57a927dc39692f1c" "a19fd2ff9d3845fdb3beffd1ea601bf329b53527d0ad8e5ecac93953f3b63637" | xxd -r -p | shasum -a 256

    Should print 575aa995fa93b290cd04afd25a3ff70f5034e864bc7b21aa79c1f042031b5fef

  4. 4. Combine step 2

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

    printf '01%s%s' "de5d72e6facc516b521a9dcc7f7d35c21eac5292319837957ba97c08d6e19a17" "575aa995fa93b290cd04afd25a3ff70f5034e864bc7b21aa79c1f042031b5fef" | xxd -r -p | shasum -a 256

    Should print 338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f

  5. 5. Combine step 3

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

    printf '01%s%s' "c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c" "338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f" | xxd -r -p | shasum -a 256

    Should print 8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

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

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

Read the specification