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-65GMMDXX Content hash 4f4e74010dabe0a3f110abb394d15284b44bc76c1e3f336d044b5f9a8c140757 Articles recorded that day 13 Attestation UID 0x99cf5acde28f98446b07d9f381ccf6b9dc4ff37ce0871d10b54a80bdb98095de View on EAS Transaction 0x61ee343cde25983c3ac3ae4c39e621400f411eefee4b607c85dfd170f3bd4190 View on Basescan 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 0xfff6a2b51a496565f1d6ad0f242253cd140d68fa17220e6853efd8a68a8945dd 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 0x3d95bdad5d03b7bb71d53e625fb19e382783b7a500c4b838de5b230d6a3da79c 0xf410fdca229ab0691b1f94711740fcba2c38059dc50db1c7cd3cffff83b079af Step 2, combined with the value after it 0x50c5d032f24d3fecf73c17b9ffbf1879eda910dd0edcb9a8ebce1a56c531365e 0x313a6fe993c1def9e9a8f850f3aa4044606c2aa7bd577952abac571c777524a9 Step 3, combined with the value after it 0x0252621b0246461f9699c1e304bdf0b1a0cb448a7f37ea1a550e00a3ca2d5f23 0x2179430ea0588befc303ccd6515f5da08e40ad99c24504fce746072a194ebe90 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 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-0917-65GMMDXX/canonical" | shasum -a 256Should print 4f4e74010dabe0a3f110abb394d15284b44bc76c1e3f336d044b5f9a8c140757
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-65GMMDXX
CONTENT=4f4e74010dabe0a3f110abb394d15284b44bc76c1e3f336d044b5f9a8c140757
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print fff6a2b51a496565f1d6ad0f242253cd140d68fa17220e6853efd8a68a8945dd
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "fff6a2b51a496565f1d6ad0f242253cd140d68fa17220e6853efd8a68a8945dd" "3d95bdad5d03b7bb71d53e625fb19e382783b7a500c4b838de5b230d6a3da79c" | xxd -r -p | shasum -a 256Should print f410fdca229ab0691b1f94711740fcba2c38059dc50db1c7cd3cffff83b079af
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "f410fdca229ab0691b1f94711740fcba2c38059dc50db1c7cd3cffff83b079af" "50c5d032f24d3fecf73c17b9ffbf1879eda910dd0edcb9a8ebce1a56c531365e" | xxd -r -p | shasum -a 256Should print 313a6fe993c1def9e9a8f850f3aa4044606c2aa7bd577952abac571c777524a9
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "313a6fe993c1def9e9a8f850f3aa4044606c2aa7bd577952abac571c777524a9" "0252621b0246461f9699c1e304bdf0b1a0cb448a7f37ea1a550e00a3ca2d5f23" | xxd -r -p | shasum -a 256Should print 2179430ea0588befc303ccd6515f5da08e40ad99c24504fce746072a194ebe90
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 256Should print 31000bb3cfb7f251ad55feede69affff43f622fc9fb42c0589e9dd15b4607a51
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/0x99cf5acde28f98446b07d9f381ccf6b9dc4ff37ce0871d10b54a80bdb98095deThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification