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-1004-GMXFE24O Content hash 38fab4e2d7a749f2c4dd8dd494301b1210daa6fd305740278b7033f48f261e1a Articles recorded that day 14 Attestation UID 0x99cd6b1d642d6f453cbd531cf2d5c5dee53a3ac0f82ed61ff6b666d95537f3be View on EAS Transaction 0x479b7310c703e960a819dd574d78be722e75921ba6309910ae4511a65681eef2 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 13 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 0x8428a1acb2cd1f5a79c7c4cef1f2fe1fa239ba33fc14ec6bbee2ef0cade6f328 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 0x5a81cd70328020758b854d72305a61c629d8f9648c310fd6f0e0132136c31389 0xa5f1f182d1b1bbfd237375b38febd9a148d1da1c210a3b3514c275990dd8560a Step 2, combined with the value after it 0xf0359591ded893c55a69d92f7169f91889989662589b3049ff43f3b3b73780b1 0xae88aafe666bca1ec42c2b36612221a4979596811c1d34b76123a88c61312a5d Step 3, combined with the value before it 0xef0e364c3bec81306843282338faec7e03a988ff384e24c70f628dcb319db925 0x56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58 Step 4, combined with the value after it 0x99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb 0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1 This is the value for the whole day.
Value these steps arrive at 0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1 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 0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1 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-1004-GMXFE24O/canonical" | shasum -a 256Should print 38fab4e2d7a749f2c4dd8dd494301b1210daa6fd305740278b7033f48f261e1a
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-1004-GMXFE24O
CONTENT=38fab4e2d7a749f2c4dd8dd494301b1210daa6fd305740278b7033f48f261e1a
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 8428a1acb2cd1f5a79c7c4cef1f2fe1fa239ba33fc14ec6bbee2ef0cade6f328
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "8428a1acb2cd1f5a79c7c4cef1f2fe1fa239ba33fc14ec6bbee2ef0cade6f328" "5a81cd70328020758b854d72305a61c629d8f9648c310fd6f0e0132136c31389" | xxd -r -p | shasum -a 256Should print a5f1f182d1b1bbfd237375b38febd9a148d1da1c210a3b3514c275990dd8560a
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "a5f1f182d1b1bbfd237375b38febd9a148d1da1c210a3b3514c275990dd8560a" "f0359591ded893c55a69d92f7169f91889989662589b3049ff43f3b3b73780b1" | xxd -r -p | shasum -a 256Should print ae88aafe666bca1ec42c2b36612221a4979596811c1d34b76123a88c61312a5d
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "ef0e364c3bec81306843282338faec7e03a988ff384e24c70f628dcb319db925" "ae88aafe666bca1ec42c2b36612221a4979596811c1d34b76123a88c61312a5d" | xxd -r -p | shasum -a 256Should print 56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58" "99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb" | xxd -r -p | shasum -a 256Should print 11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1
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/0x99cd6b1d642d6f453cbd531cf2d5c5dee53a3ac0f82ed61ff6b666d95537f3beThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification