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-22SBYEOS Content hash e7c7f7b9e0e28fa06cb7f6337e6c14a26902ced659fece8e9d08023906dff782 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 0x047fb6b0704293537dcab9bb395021d30662ce660d95a4cec66d304887d043f1 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 0x0712feb351f444ff25d0dfce596dff94061305b00059f5a98577aabd29b8d739 0x38fd72cec5758f158a122d0559684bdaf0c04219b07b442b0446ddf067ef6314 Step 2, combined with the value after it 0x0e07876838056510f078754761c3f40914a93e2e68b6d902bdc515a50f064a48 0x8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d Step 3, combined with the value after it 0x33f6777026ff7882413ac506d5f631b15881c5c97af38b1bb507519f8ad7059a 0xd47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a Step 4, combined with the value after it 0x9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb 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.
{"abstract":null,"agreement":false,"authors":[{"identity":"RoboNextGen","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"Robot Bar","src":"https://media.vitahash.org/articles/540cd9e3-acca-4916-9982-945a526b9…Copy this text, paste it into any SHA-256 tool, and compare the result with the hash shown above. If the two match, this is exactly what Vitahash recorded.
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-22SBYEOS/canonical" | shasum -a 256Should print e7c7f7b9e0e28fa06cb7f6337e6c14a26902ced659fece8e9d08023906dff782
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-22SBYEOS
CONTENT=e7c7f7b9e0e28fa06cb7f6337e6c14a26902ced659fece8e9d08023906dff782
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 047fb6b0704293537dcab9bb395021d30662ce660d95a4cec66d304887d043f1
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "047fb6b0704293537dcab9bb395021d30662ce660d95a4cec66d304887d043f1" "0712feb351f444ff25d0dfce596dff94061305b00059f5a98577aabd29b8d739" | xxd -r -p | shasum -a 256Should print 38fd72cec5758f158a122d0559684bdaf0c04219b07b442b0446ddf067ef6314
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "38fd72cec5758f158a122d0559684bdaf0c04219b07b442b0446ddf067ef6314" "0e07876838056510f078754761c3f40914a93e2e68b6d902bdc515a50f064a48" | xxd -r -p | shasum -a 256Should print 8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d" "33f6777026ff7882413ac506d5f631b15881c5c97af38b1bb507519f8ad7059a" | xxd -r -p | shasum -a 256Should print d47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a
6. Combine step 4 The value you have goes first, then the published value.
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