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-0914-QGNOG5I5 Content hash d7097a088b51ddda7ce05441f87f31946849517fd59a02101c368c96b8d0a4bc Articles recorded that day 9 Attestation UID 0x736e30d14213497219ae6c7039b354a5b9300b96a9f3cb6b892242a1ab4eced5 View on EAS Transaction 0x5636b4f32543f00d51d78228c9e4ec0aea3b72c65414dea4c9a52fad1e010cc4 View on Basescan Recorded on Base using canonicalization v1 and record format v1.
How this article reaches the blockchain It was combined with the other 8 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 0x88671d848f33f12b8d9dba6658416767c5183c547d42be6672d5517fb3bac161 Built from this article's content hash and its stamp ID, as sha256(0x00 || sha256(utf8(stampId)) || contentHash).
Step 1, combined with the value after it 0x0e363495fd00c4f6027a8d16f16f48ebc5dd98a4445cb2fda19d68ab226d54a2 0x8add037858dabf7aaad10a10454c6d84d53f4c5bc3c24560439f9b32c9a126b8 Step 2, combined with the value before it 0xd41b76b2e50e1ffa5d38a084ccd879ffde85d16c3c73f52f0966f7e24d50ee46 0x48994e7e42121815df110b6d53fb4041d332b11f10e6c1cacfe9393c557dd105 Step 3, combined with the value before it 0xdf07cf87f403a6dfbb8317e41b33117f5227f3a6550bc1a5ffb4ec7174b292eb 0x65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d Step 4, combined with the value after it 0x35da83a97073db5f8da92cb90a2bd4462d5e3e44ca84a177f09a70fdc13eb4d4 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de This is the value for the whole day.
Value these steps arrive at 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de 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 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de 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.
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-0914-QGNOG5I5/canonical" | shasum -a 256Should print d7097a088b51ddda7ce05441f87f31946849517fd59a02101c368c96b8d0a4bc
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-0914-QGNOG5I5
CONTENT=d7097a088b51ddda7ce05441f87f31946849517fd59a02101c368c96b8d0a4bc
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 88671d848f33f12b8d9dba6658416767c5183c547d42be6672d5517fb3bac161
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "88671d848f33f12b8d9dba6658416767c5183c547d42be6672d5517fb3bac161" "0e363495fd00c4f6027a8d16f16f48ebc5dd98a4445cb2fda19d68ab226d54a2" | xxd -r -p | shasum -a 256Should print 8add037858dabf7aaad10a10454c6d84d53f4c5bc3c24560439f9b32c9a126b8
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "d41b76b2e50e1ffa5d38a084ccd879ffde85d16c3c73f52f0966f7e24d50ee46" "8add037858dabf7aaad10a10454c6d84d53f4c5bc3c24560439f9b32c9a126b8" | xxd -r -p | shasum -a 256Should print 48994e7e42121815df110b6d53fb4041d332b11f10e6c1cacfe9393c557dd105
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "df07cf87f403a6dfbb8317e41b33117f5227f3a6550bc1a5ffb4ec7174b292eb" "48994e7e42121815df110b6d53fb4041d332b11f10e6c1cacfe9393c557dd105" | xxd -r -p | shasum -a 256Should print 65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d" "35da83a97073db5f8da92cb90a2bd4462d5e3e44ca84a177f09a70fdc13eb4d4" | xxd -r -p | shasum -a 256Should print 629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de
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/0x736e30d14213497219ae6c7039b354a5b9300b96a9f3cb6b892242a1ab4eced5The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification