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-0920-5UDVKOVG Content hash 2b43a43305b43c23cc4faa11b084c82557d7ae00d8686978c39ea034e5320453 Articles recorded that day 19 Attestation UID 0x8b3c2fd36a922edc6b9b5df7a32564ad6b8254e5e4d73310406d45385ea13aef View on EAS Transaction 0x7487c62e52e4f2f9b08c668465c50f1ad9bf79791f45570457388f46bcdbb8aa 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 18 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 0x765427af27e106c13526ca1b6994ddb75a1404fa5ee4461f343eb15a784f6953 Built from this article's content hash and its stamp ID, as sha256(0x00 || sha256(utf8(stampId)) || contentHash).
Step 1, combined with the value before it 0x5154c5770ced2973bf34cef7d48e6ae5fbd7efb2bd081c2889f89048d09a390c 0x0c8b677f8e343e5e21601e62f6fa2f8f238515f80ec93a3733e7fedc3bdb102b Step 2, combined with the value after it 0x0aaf99524c4ce722f6307b65cab805bdadcaddf122d1a1fce2325c13bfd35cfe 0xecec0fa3a92582e51cab9664b82d8f67ce0b9ba9fe0766904b0f2fec6b0796d9 Step 3, combined with the value after it 0xe5d0f70bc2a34d3af94354d76ac8b0828eec65a971d8cc2919b2c3a443ac48e4 0x6e74ab88876a58402acac210af008b9f1012f01a329a0a8a206ba9a146828ecc Step 4, combined with the value after it 0xa65919732d1594acc9afb550ed2ce10e8bf96a42ea9b49984733673443822e5e 0x2e6ebaca17a3bf1331e377895837d2a1ed000ada39219e6311b1166e1f7b9603 Step 5, combined with the value after it 0x9ea770e708ff5a992ebbe1dc432ce6a573002e55cb9a4793a315029f9ce7b7ec 0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31 This is the value for the whole day.
Value these steps arrive at 0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31 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 0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31 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-0920-5UDVKOVG/canonical" | shasum -a 256Should print 2b43a43305b43c23cc4faa11b084c82557d7ae00d8686978c39ea034e5320453
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-0920-5UDVKOVG
CONTENT=2b43a43305b43c23cc4faa11b084c82557d7ae00d8686978c39ea034e5320453
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 765427af27e106c13526ca1b6994ddb75a1404fa5ee4461f343eb15a784f6953
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "5154c5770ced2973bf34cef7d48e6ae5fbd7efb2bd081c2889f89048d09a390c" "765427af27e106c13526ca1b6994ddb75a1404fa5ee4461f343eb15a784f6953" | xxd -r -p | shasum -a 256Should print 0c8b677f8e343e5e21601e62f6fa2f8f238515f80ec93a3733e7fedc3bdb102b
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "0c8b677f8e343e5e21601e62f6fa2f8f238515f80ec93a3733e7fedc3bdb102b" "0aaf99524c4ce722f6307b65cab805bdadcaddf122d1a1fce2325c13bfd35cfe" | xxd -r -p | shasum -a 256Should print ecec0fa3a92582e51cab9664b82d8f67ce0b9ba9fe0766904b0f2fec6b0796d9
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "ecec0fa3a92582e51cab9664b82d8f67ce0b9ba9fe0766904b0f2fec6b0796d9" "e5d0f70bc2a34d3af94354d76ac8b0828eec65a971d8cc2919b2c3a443ac48e4" | xxd -r -p | shasum -a 256Should print 6e74ab88876a58402acac210af008b9f1012f01a329a0a8a206ba9a146828ecc
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "6e74ab88876a58402acac210af008b9f1012f01a329a0a8a206ba9a146828ecc" "a65919732d1594acc9afb550ed2ce10e8bf96a42ea9b49984733673443822e5e" | xxd -r -p | shasum -a 256Should print 2e6ebaca17a3bf1331e377895837d2a1ed000ada39219e6311b1166e1f7b9603
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "2e6ebaca17a3bf1331e377895837d2a1ed000ada39219e6311b1166e1f7b9603" "9ea770e708ff5a992ebbe1dc432ce6a573002e55cb9a4793a315029f9ce7b7ec" | xxd -r -p | shasum -a 256Should print 86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31
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/0x8b3c2fd36a922edc6b9b5df7a32564ad6b8254e5e4d73310406d45385ea13aefThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification