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-0916-ULUU2F4K Content hash 8a9415b804058aacae4c04743662540f8d088dbf95711f89647c73126feddb49 Articles recorded that day 13 Attestation UID 0xc7ecca8e299e46ef24d229b828425ddc4df5cbe7be90f2ed4da17d210ba98dcf View on EAS Transaction 0x802c4a507338c8f50008399b88a0a1cfc21449223c52c9d2999e95302a297901 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 0x8609247c6731d0aa358a8b6c928449cff292411831214499a9f868066d9b6187 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 0x66c74b97e7f4d67556f514894114e588bbfa75f6d11e03188620846bb5419870 0x722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3 Step 2, combined with the value after it 0xc2cff0e6b49334b70f53dfc7778c629dd7d919216f3f1ed0eb9ab28975d11a97 0x6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81 Step 3, combined with the value after it 0x6e4be1cffefe4e47dd9c1e392584b255ee6b3194fc365604138274b8f4f37e4e 0x40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576 Step 4, combined with the value before it 0xf079b4aa3e8888febddac6d9c23b9a16ae9e54868fbc4964eabfcd6436ae4c94 0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996 This is the value for the whole day.
Value these steps arrive at 0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996 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 0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996 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-0916-ULUU2F4K/canonical" | shasum -a 256Should print 8a9415b804058aacae4c04743662540f8d088dbf95711f89647c73126feddb49
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-0916-ULUU2F4K
CONTENT=8a9415b804058aacae4c04743662540f8d088dbf95711f89647c73126feddb49
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 8609247c6731d0aa358a8b6c928449cff292411831214499a9f868066d9b6187
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "8609247c6731d0aa358a8b6c928449cff292411831214499a9f868066d9b6187" "66c74b97e7f4d67556f514894114e588bbfa75f6d11e03188620846bb5419870" | xxd -r -p | shasum -a 256Should print 722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3" "c2cff0e6b49334b70f53dfc7778c629dd7d919216f3f1ed0eb9ab28975d11a97" | xxd -r -p | shasum -a 256Should print 6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81" "6e4be1cffefe4e47dd9c1e392584b255ee6b3194fc365604138274b8f4f37e4e" | xxd -r -p | shasum -a 256Should print 40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "f079b4aa3e8888febddac6d9c23b9a16ae9e54868fbc4964eabfcd6436ae4c94" "40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576" | xxd -r -p | shasum -a 256Should print 6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996
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/0xc7ecca8e299e46ef24d229b828425ddc4df5cbe7be90f2ed4da17d210ba98dcfThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification