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-0925-FYZUG65J Content hash da424df909ab42a443e7fc2c84a1d3daaad183dd86b36f5a0a0509914245b42a Articles recorded that day 20 Attestation UID 0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44 View on EAS Transaction 0x8773b62d3c7fe3c39180795fdbf303e39a988305339fd36d0f85017972c0bcd5 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 19 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 0x65e0af2f7d136c197cbdea8c63df8554c63e7e9d1c131eb0e243e1b48d51ff5b 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 0xdbe80902477d9ec24f9eb9e508ef3a0525e6fd73d4212d1c0499ca7cd4dffc44 0x9d6fb35e8e58207102e3ed020fca09d20c145529f114e1d058ed956c08f5017b Step 2, combined with the value after it 0x79386d44ad3efbf8bc07c8616d233c050359dc8a0eef738182adc8dd6810539a 0x1c5adf9f24c1361259bd3f75f752da821657b46f72772b585ff2cbfc77870e91 Step 3, combined with the value after it 0x8c5e0bcdad701cf810b7c1d35001164268482c86a64c1e579bccb96aafd48ee4 0xeef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba Step 4, combined with the value before it 0x97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb 0xc1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c Step 5, combined with the value after it 0x338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f 0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab This is the value for the whole day.
Value these steps arrive at 0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab 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 0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab 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-0925-FYZUG65J/canonical" | shasum -a 256Should print da424df909ab42a443e7fc2c84a1d3daaad183dd86b36f5a0a0509914245b42a
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-0925-FYZUG65J
CONTENT=da424df909ab42a443e7fc2c84a1d3daaad183dd86b36f5a0a0509914245b42a
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 65e0af2f7d136c197cbdea8c63df8554c63e7e9d1c131eb0e243e1b48d51ff5b
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "65e0af2f7d136c197cbdea8c63df8554c63e7e9d1c131eb0e243e1b48d51ff5b" "dbe80902477d9ec24f9eb9e508ef3a0525e6fd73d4212d1c0499ca7cd4dffc44" | xxd -r -p | shasum -a 256Should print 9d6fb35e8e58207102e3ed020fca09d20c145529f114e1d058ed956c08f5017b
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "9d6fb35e8e58207102e3ed020fca09d20c145529f114e1d058ed956c08f5017b" "79386d44ad3efbf8bc07c8616d233c050359dc8a0eef738182adc8dd6810539a" | xxd -r -p | shasum -a 256Should print 1c5adf9f24c1361259bd3f75f752da821657b46f72772b585ff2cbfc77870e91
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "1c5adf9f24c1361259bd3f75f752da821657b46f72772b585ff2cbfc77870e91" "8c5e0bcdad701cf810b7c1d35001164268482c86a64c1e579bccb96aafd48ee4" | xxd -r -p | shasum -a 256Should print eef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb" "eef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba" | xxd -r -p | shasum -a 256Should print c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c" "338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f" | xxd -r -p | shasum -a 256Should print 8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
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/0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification