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-0930-BGHPOQMG Content hash 56401b0f48332a84c426dde0269b6dc91ad0723e4f76ffe131ba45c864e88339 Articles recorded that day 19 Attestation UID 0x603b46532a7efbd9420f294207f0abcd39e475cccc5bcbbe0e361a4bb85dbbbe View on EAS Transaction 0x542521066dc4058a3602b27ff9baa48863be20de6eaa6baaadb6df2c602e64ab 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 0xcdfe2d83fc7b8cf8ee1030e151fc0aed1e9b86e0c040ef71eabbf6ac34b2edd4 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 0x9c604bf073696bf84f520cafe5669112288eb6e6bd9aff2d90c69014653fbd2e 0x73c6ea2607673d910e22b64311210d80bd7c086445d953d743c5bff12401a3a0 Step 2, combined with the value before it 0xdde0bb39f28399964bcc75f67b9ebe8fdf72b21186bc5317dba26f2bb5f32ac5 0xf5ca5212eb7b386f27b278faba727e8f416dfa75b2e3165fb1980386ef538f84 Step 3, combined with the value after it 0x2b68bd6b5bbfd613fb4b6e577cf7432b5e3b6532528a42e8753648dfca00420b 0x787621a4178b6e49933122f88a9ce82eac89c191e91b57f0fa099d31def8f00b Step 4, combined with the value after it 0xfb1af2902d2398d75ebcddae6fd629a2a64746c29c4a7449e07bad3292332261 0xa572e1caf0ceea7eeefbfdc95285c283f2e0c69a76251d97d02813de8af7832b Step 5, combined with the value after it 0xcf24b85b1c54001ae98242451fdf6ac7d16199d8241d31c4592832adbcb4f53c 0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be This is the value for the whole day.
Value these steps arrive at 0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be 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 0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be 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-0930-BGHPOQMG/canonical" | shasum -a 256Should print 56401b0f48332a84c426dde0269b6dc91ad0723e4f76ffe131ba45c864e88339
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-0930-BGHPOQMG
CONTENT=56401b0f48332a84c426dde0269b6dc91ad0723e4f76ffe131ba45c864e88339
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print cdfe2d83fc7b8cf8ee1030e151fc0aed1e9b86e0c040ef71eabbf6ac34b2edd4
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "cdfe2d83fc7b8cf8ee1030e151fc0aed1e9b86e0c040ef71eabbf6ac34b2edd4" "9c604bf073696bf84f520cafe5669112288eb6e6bd9aff2d90c69014653fbd2e" | xxd -r -p | shasum -a 256Should print 73c6ea2607673d910e22b64311210d80bd7c086445d953d743c5bff12401a3a0
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "dde0bb39f28399964bcc75f67b9ebe8fdf72b21186bc5317dba26f2bb5f32ac5" "73c6ea2607673d910e22b64311210d80bd7c086445d953d743c5bff12401a3a0" | xxd -r -p | shasum -a 256Should print f5ca5212eb7b386f27b278faba727e8f416dfa75b2e3165fb1980386ef538f84
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "f5ca5212eb7b386f27b278faba727e8f416dfa75b2e3165fb1980386ef538f84" "2b68bd6b5bbfd613fb4b6e577cf7432b5e3b6532528a42e8753648dfca00420b" | xxd -r -p | shasum -a 256Should print 787621a4178b6e49933122f88a9ce82eac89c191e91b57f0fa099d31def8f00b
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "787621a4178b6e49933122f88a9ce82eac89c191e91b57f0fa099d31def8f00b" "fb1af2902d2398d75ebcddae6fd629a2a64746c29c4a7449e07bad3292332261" | xxd -r -p | shasum -a 256Should print a572e1caf0ceea7eeefbfdc95285c283f2e0c69a76251d97d02813de8af7832b
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "a572e1caf0ceea7eeefbfdc95285c283f2e0c69a76251d97d02813de8af7832b" "cf24b85b1c54001ae98242451fdf6ac7d16199d8241d31c4592832adbcb4f53c" | xxd -r -p | shasum -a 256Should print 20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be
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/0x603b46532a7efbd9420f294207f0abcd39e475cccc5bcbbe0e361a4bb85dbbbeThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification