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-0912-JVYMPAIF Content hash 1e4bd1378c9fdf7768647adf63391acacf47271a52c28f392e23e4a73917b426 Articles recorded that day 12 Attestation UID 0xe3d8bd2eb8f03a62049ad18692cb77891d5172e148e4d05da8c0caa3a3d19861 View on EAS Transaction 0x805d0579370308945e4cd9dcbcee7ba593bbae37a839bbee40333a5f4845cf0a View on Basescan Recorded on Base using canonicalization v1 and record format v1.
How this article reaches the blockchain It was combined with the other 11 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 0x4cdfb723390f8d1189cb7d42d85c3c19ed9c74553a59732c32902eaf78dfa0b6 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 0xdec094ee927bdc54949ee1d5cc5d421ef948487ae5b71beacb96ecb477948096 0xd6fed92f3021becb84cde40226641c27eec2b714d6359e843ac3d08e48bbc861 Step 2, combined with the value after it 0x78361e3aa74de301f74ec2521dcf30c4b23379d18c055b8694b1efae0b4e9030 0x53bbed2004c53646a2a586c47a8cfdf797ef798abd97d6dd0669e6410d17738a Step 3, combined with the value before it 0x93547a393e45808d36a7b5d9f66bce908ac1118915cc89c6641bf4b3ead4601e 0x7a5d92dadcf9090e0ca98ca0332b44c973c20ce01f4370a0e1e7c59929bb124b Step 4, combined with the value after it 0x8d23c52490116aed9c6806c460a82c2867e0d8fa16cde80f349574b442de9011 0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3 This is the value for the whole day.
Value these steps arrive at 0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3 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 0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3 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-0912-JVYMPAIF/canonical" | shasum -a 256Should print 1e4bd1378c9fdf7768647adf63391acacf47271a52c28f392e23e4a73917b426
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-0912-JVYMPAIF
CONTENT=1e4bd1378c9fdf7768647adf63391acacf47271a52c28f392e23e4a73917b426
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 4cdfb723390f8d1189cb7d42d85c3c19ed9c74553a59732c32902eaf78dfa0b6
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "dec094ee927bdc54949ee1d5cc5d421ef948487ae5b71beacb96ecb477948096" "4cdfb723390f8d1189cb7d42d85c3c19ed9c74553a59732c32902eaf78dfa0b6" | xxd -r -p | shasum -a 256Should print d6fed92f3021becb84cde40226641c27eec2b714d6359e843ac3d08e48bbc861
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "d6fed92f3021becb84cde40226641c27eec2b714d6359e843ac3d08e48bbc861" "78361e3aa74de301f74ec2521dcf30c4b23379d18c055b8694b1efae0b4e9030" | xxd -r -p | shasum -a 256Should print 53bbed2004c53646a2a586c47a8cfdf797ef798abd97d6dd0669e6410d17738a
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "93547a393e45808d36a7b5d9f66bce908ac1118915cc89c6641bf4b3ead4601e" "53bbed2004c53646a2a586c47a8cfdf797ef798abd97d6dd0669e6410d17738a" | xxd -r -p | shasum -a 256Should print 7a5d92dadcf9090e0ca98ca0332b44c973c20ce01f4370a0e1e7c59929bb124b
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "7a5d92dadcf9090e0ca98ca0332b44c973c20ce01f4370a0e1e7c59929bb124b" "8d23c52490116aed9c6806c460a82c2867e0d8fa16cde80f349574b442de9011" | xxd -r -p | shasum -a 256Should print afe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3
7. 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/0xe3d8bd2eb8f03a62049ad18692cb77891d5172e148e4d05da8c0caa3a3d19861The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification