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-0913-IPROOE6B Content hash 92b0aa203af1759ff07383ed2a85768e9f70398e43fdc176f86d4dddd0669ab5 Articles recorded that day 10 Attestation UID 0x73ee082688da54567d01b1f22436046f13656591449ce75624d7ae0330722f64 View on EAS Transaction 0xa31c0f039845fb24a569dd2e436934c516b0c7d290877bb44318f5d4757ec286 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 9 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 0xf5f8eb8d0b6fb89fa48bdf655ecf7c9177d461db7f3228530f7360f07d6510c2 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 0xf132a8316eaef8176455738a76429b55d2f7025558009e1d63d77ca829f69b2b 0x2e65dba0402bcb3033160f9d48e9ef5c4c3b7601a9f48909680baf36538190f0 Step 2, combined with the value before it 0xd3bb711b215c6f8b83a52bead900b146a2565c844d5902caedcd1d06b782efee 0xa0e9279f5f2ed6bab26877d2bd3950645ededd8fe7994a5bacb5a1bd78752b06 Step 3, combined with the value after it 0x90117b787e8b3ab3d5080631e961f662f0b5b874bed0118b36d17c71c6d19dfc 0x3ee1154344afd5ca878daeb2a44f60a4a365c7ba6c4c0867a7a5b2b32806e8ab Step 4, combined with the value after it 0xa5b35a004d75025ccc762630a62487ebda6adcc9ca381428cbe21851b81de5ab 0x6fa2d26a7c3adb0192369434bfd7bc5de3702a47810e7e9fa5f913a011fdecb5 This is the value for the whole day.
Value these steps arrive at 0x6fa2d26a7c3adb0192369434bfd7bc5de3702a47810e7e9fa5f913a011fdecb5 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 0x6fa2d26a7c3adb0192369434bfd7bc5de3702a47810e7e9fa5f913a011fdecb5 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-0913-IPROOE6B/canonical" | shasum -a 256Should print 92b0aa203af1759ff07383ed2a85768e9f70398e43fdc176f86d4dddd0669ab5
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-0913-IPROOE6B
CONTENT=92b0aa203af1759ff07383ed2a85768e9f70398e43fdc176f86d4dddd0669ab5
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print f5f8eb8d0b6fb89fa48bdf655ecf7c9177d461db7f3228530f7360f07d6510c2
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "f5f8eb8d0b6fb89fa48bdf655ecf7c9177d461db7f3228530f7360f07d6510c2" "f132a8316eaef8176455738a76429b55d2f7025558009e1d63d77ca829f69b2b" | xxd -r -p | shasum -a 256Should print 2e65dba0402bcb3033160f9d48e9ef5c4c3b7601a9f48909680baf36538190f0
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "d3bb711b215c6f8b83a52bead900b146a2565c844d5902caedcd1d06b782efee" "2e65dba0402bcb3033160f9d48e9ef5c4c3b7601a9f48909680baf36538190f0" | xxd -r -p | shasum -a 256Should print a0e9279f5f2ed6bab26877d2bd3950645ededd8fe7994a5bacb5a1bd78752b06
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "a0e9279f5f2ed6bab26877d2bd3950645ededd8fe7994a5bacb5a1bd78752b06" "90117b787e8b3ab3d5080631e961f662f0b5b874bed0118b36d17c71c6d19dfc" | xxd -r -p | shasum -a 256Should print 3ee1154344afd5ca878daeb2a44f60a4a365c7ba6c4c0867a7a5b2b32806e8ab
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "3ee1154344afd5ca878daeb2a44f60a4a365c7ba6c4c0867a7a5b2b32806e8ab" "a5b35a004d75025ccc762630a62487ebda6adcc9ca381428cbe21851b81de5ab" | xxd -r -p | shasum -a 256Should print 6fa2d26a7c3adb0192369434bfd7bc5de3702a47810e7e9fa5f913a011fdecb5
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/0x73ee082688da54567d01b1f22436046f13656591449ce75624d7ae0330722f64The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification