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-0924-UEEI7PAB Content hash 44f882462de1e060e021f0c3f7e6aa8ce18c8b3e3d37766fde871dc5ad8c9f9f Articles recorded that day 17 Attestation UID 0xb24b7d03fcf1c37c404222c77aea8f23a7442f446db95e1d2e25fb5019c66a91 View on EAS Transaction 0xc7ded12887c12bc50ffa01bd0e2c191c565b72fca5dd7bece3f89cd683f3d759 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 16 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 0xedbceaed0417688870c20643f0bd66a721f922fb84d0f3a3be2fed6cce13c78f 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 0x0785160769cadb662ccb546e587fea3e203ea5c4753af49e4430a823a68c3fbe 0x2dfaed8286a95551d53ab8e4536ace273834ba83c5ab63b984988918bc94ebc7 Step 2, combined with the value before it 0xee857f5cbff855a18cb8ee83b8701e77a4375dbe0ad8d8d49c2887efdafe6390 0x43f86af44fb2bbf68cf5f3e94d1d2b5ced2d5ebf59c5e44b26698123130a18e7 Step 3, combined with the value before it 0x9d6fa85f6dcc73de694f40b22fcb8b2117a9058cc64e675fec7fef47d0cb3caf 0x9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb Step 4, combined with the value before it 0xd47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a 0x23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b Step 5, combined with the value after it 0x33c71efd9544bcb45a34807054911137e217cec8f6485b60035b69b93011a650 0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4 This is the value for the whole day.
Value these steps arrive at 0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4 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 0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4 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-0924-UEEI7PAB/canonical" | shasum -a 256Should print 44f882462de1e060e021f0c3f7e6aa8ce18c8b3e3d37766fde871dc5ad8c9f9f
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-0924-UEEI7PAB
CONTENT=44f882462de1e060e021f0c3f7e6aa8ce18c8b3e3d37766fde871dc5ad8c9f9f
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print edbceaed0417688870c20643f0bd66a721f922fb84d0f3a3be2fed6cce13c78f
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "edbceaed0417688870c20643f0bd66a721f922fb84d0f3a3be2fed6cce13c78f" "0785160769cadb662ccb546e587fea3e203ea5c4753af49e4430a823a68c3fbe" | xxd -r -p | shasum -a 256Should print 2dfaed8286a95551d53ab8e4536ace273834ba83c5ab63b984988918bc94ebc7
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "ee857f5cbff855a18cb8ee83b8701e77a4375dbe0ad8d8d49c2887efdafe6390" "2dfaed8286a95551d53ab8e4536ace273834ba83c5ab63b984988918bc94ebc7" | xxd -r -p | shasum -a 256Should print 43f86af44fb2bbf68cf5f3e94d1d2b5ced2d5ebf59c5e44b26698123130a18e7
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "9d6fa85f6dcc73de694f40b22fcb8b2117a9058cc64e675fec7fef47d0cb3caf" "43f86af44fb2bbf68cf5f3e94d1d2b5ced2d5ebf59c5e44b26698123130a18e7" | xxd -r -p | shasum -a 256Should print 9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "d47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a" "9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb" | xxd -r -p | shasum -a 256Should print 23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b" "33c71efd9544bcb45a34807054911137e217cec8f6485b60035b69b93011a650" | xxd -r -p | shasum -a 256Should print f5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4
8. 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/0xb24b7d03fcf1c37c404222c77aea8f23a7442f446db95e1d2e25fb5019c66a91The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification