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-0914-7RCZ7CM3 Content hash 1c8d1d48bb45d9481b8c865fa810364abc58a1099d384555469c56f55b43cedc Articles recorded that day 9 Attestation UID 0x736e30d14213497219ae6c7039b354a5b9300b96a9f3cb6b892242a1ab4eced5 View on EAS Transaction 0x5636b4f32543f00d51d78228c9e4ec0aea3b72c65414dea4c9a52fad1e010cc4 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 8 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 0x30065996bb53f57509cc756f12a9bd022c8b71b7d26077164be9ad27aa2181a8 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 0xa1785e4a65d4d05192e6d4ec29464a726bfee9359602e5137cf7583574ae6fe1 0x0403bf06fd6bb55eaeb5e9110eb647fdf84c27edd66c2de58628538a04552710 Step 2, combined with the value before it 0x33812d543853277fd23680897ffd62dd040a8a53467e6399981082bddf5bacf2 0xdf07cf87f403a6dfbb8317e41b33117f5227f3a6550bc1a5ffb4ec7174b292eb Step 3, combined with the value after it 0x48994e7e42121815df110b6d53fb4041d332b11f10e6c1cacfe9393c557dd105 0x65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d Step 4, combined with the value after it 0x35da83a97073db5f8da92cb90a2bd4462d5e3e44ca84a177f09a70fdc13eb4d4 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de This is the value for the whole day.
Value these steps arrive at 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de 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 0x629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de 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-0914-7RCZ7CM3/canonical" | shasum -a 256Should print 1c8d1d48bb45d9481b8c865fa810364abc58a1099d384555469c56f55b43cedc
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-0914-7RCZ7CM3
CONTENT=1c8d1d48bb45d9481b8c865fa810364abc58a1099d384555469c56f55b43cedc
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 30065996bb53f57509cc756f12a9bd022c8b71b7d26077164be9ad27aa2181a8
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "30065996bb53f57509cc756f12a9bd022c8b71b7d26077164be9ad27aa2181a8" "a1785e4a65d4d05192e6d4ec29464a726bfee9359602e5137cf7583574ae6fe1" | xxd -r -p | shasum -a 256Should print 0403bf06fd6bb55eaeb5e9110eb647fdf84c27edd66c2de58628538a04552710
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "33812d543853277fd23680897ffd62dd040a8a53467e6399981082bddf5bacf2" "0403bf06fd6bb55eaeb5e9110eb647fdf84c27edd66c2de58628538a04552710" | xxd -r -p | shasum -a 256Should print df07cf87f403a6dfbb8317e41b33117f5227f3a6550bc1a5ffb4ec7174b292eb
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "df07cf87f403a6dfbb8317e41b33117f5227f3a6550bc1a5ffb4ec7174b292eb" "48994e7e42121815df110b6d53fb4041d332b11f10e6c1cacfe9393c557dd105" | xxd -r -p | shasum -a 256Should print 65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "65a90853786338e3cccdc846bd6a14de78265fafbf3d88d39c417e4b9ea8a69d" "35da83a97073db5f8da92cb90a2bd4462d5e3e44ca84a177f09a70fdc13eb4d4" | xxd -r -p | shasum -a 256Should print 629fbf8d6325b4d78c8d60f0b560b68f539c5068124dd214da4aa2b69eb708de
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/0x736e30d14213497219ae6c7039b354a5b9300b96a9f3cb6b892242a1ab4eced5The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification