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-0923-3IVB25UK Content hash a185180faf1a909c88c62a5eaa82c07ee3f3e17fc672da5765fdca0b33da7023 Articles recorded that day 17 Attestation UID 0x762e6311ed34312a3f3132a6182a8042fbfb824a36d9ae6d78578c9b6b802645 View on EAS Transaction 0xe6f94b9a91b705afc7d83ce1a42a74215dde7d1a18a31b24220210388e2cdc0a 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 0xdfcaf6dcd80d94f27cc502106130d36e49024e2feb2031bd2b3da62dc8299b4f 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 0x8bd1d263dcd03efc0e56ff2808e5ef9a967a542a1367388acc4a43c736b804b5 0x4705303e65492c35e836124c2442ecf46a01cc245e26bf113f03e802d583ff43 Step 2, combined with the value after it 0xf3d97edf31481865e031c9bb09578a8f316dbc6a5f8cc38736e356168954577e 0x0f4cdf5e49c3556651293c95b323d3c9c6b081975eaafbd69902f50918a03467 Step 3, combined with the value after it 0x810a0b87471478bacdd40b4ec2941408a4bfd4a2d74f3ee06b6f74191b567cf1 0x580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44 Step 4, combined with the value after it 0x7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39 0xcc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26 Step 5, combined with the value after it 0x84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d 0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec This is the value for the whole day.
Value these steps arrive at 0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec 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 0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec 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":"90sTimeCapsule","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"Furby","src":"https://media.vitahash.org/articles/abccf150-454e-42e1-b438-0420f70fcf…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-0923-3IVB25UK/canonical" | shasum -a 256Should print a185180faf1a909c88c62a5eaa82c07ee3f3e17fc672da5765fdca0b33da7023
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-0923-3IVB25UK
CONTENT=a185180faf1a909c88c62a5eaa82c07ee3f3e17fc672da5765fdca0b33da7023
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print dfcaf6dcd80d94f27cc502106130d36e49024e2feb2031bd2b3da62dc8299b4f
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "dfcaf6dcd80d94f27cc502106130d36e49024e2feb2031bd2b3da62dc8299b4f" "8bd1d263dcd03efc0e56ff2808e5ef9a967a542a1367388acc4a43c736b804b5" | xxd -r -p | shasum -a 256Should print 4705303e65492c35e836124c2442ecf46a01cc245e26bf113f03e802d583ff43
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "4705303e65492c35e836124c2442ecf46a01cc245e26bf113f03e802d583ff43" "f3d97edf31481865e031c9bb09578a8f316dbc6a5f8cc38736e356168954577e" | xxd -r -p | shasum -a 256Should print 0f4cdf5e49c3556651293c95b323d3c9c6b081975eaafbd69902f50918a03467
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "0f4cdf5e49c3556651293c95b323d3c9c6b081975eaafbd69902f50918a03467" "810a0b87471478bacdd40b4ec2941408a4bfd4a2d74f3ee06b6f74191b567cf1" | xxd -r -p | shasum -a 256Should print 580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44" "7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39" | xxd -r -p | shasum -a 256Should print cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26" "84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d" | xxd -r -p | shasum -a 256Should print 0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec
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/0x762e6311ed34312a3f3132a6182a8042fbfb824a36d9ae6d78578c9b6b802645The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification