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-1006-AUC2BVAG Content hash ccbe327a7e674e2af42f2f698a528116ff52d0e2b334e5257bb419346bf86ffb Articles recorded that day 16 Attestation UID 0x2838e247dcdc03d7e5d3def4582bb14c0fd666fbfbca325ed921536c8267f446 View on EAS Transaction 0x70789bf19e02a7f6c3d6d64f551810889fee56d00e65909f037a2b329b146784 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 15 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 0x50bd57c866568e532dd18e984567c467aa60068b25d99ae91ab79bcd289d8825 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 0xabb8e205c3004a8d30f26afac9a96ba3a5fd37ca05fc4f1c6472dd58b73a182d 0xb807a4aee9c2c2e74bfa1d48fc1aff37cc8b8c5b0aabfe0a23b87c522c1cedfd Step 2, combined with the value after it 0x7a64f201e7db64d6a36718004c9e79bea1063fe00f3b7f2df5d7f86f44c5831b 0xfe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae Step 3, combined with the value before it 0xaae3dbfe1e75ecdb701a8693a80198ff7daad62daa02bb5a7061ee9a35094929 0x531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5 Step 4, combined with the value after it 0xf7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4 0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07 This is the value for the whole day.
Value these steps arrive at 0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07 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 0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07 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-1006-AUC2BVAG/canonical" | shasum -a 256Should print ccbe327a7e674e2af42f2f698a528116ff52d0e2b334e5257bb419346bf86ffb
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-1006-AUC2BVAG
CONTENT=ccbe327a7e674e2af42f2f698a528116ff52d0e2b334e5257bb419346bf86ffb
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 50bd57c866568e532dd18e984567c467aa60068b25d99ae91ab79bcd289d8825
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "50bd57c866568e532dd18e984567c467aa60068b25d99ae91ab79bcd289d8825" "abb8e205c3004a8d30f26afac9a96ba3a5fd37ca05fc4f1c6472dd58b73a182d" | xxd -r -p | shasum -a 256Should print b807a4aee9c2c2e74bfa1d48fc1aff37cc8b8c5b0aabfe0a23b87c522c1cedfd
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "b807a4aee9c2c2e74bfa1d48fc1aff37cc8b8c5b0aabfe0a23b87c522c1cedfd" "7a64f201e7db64d6a36718004c9e79bea1063fe00f3b7f2df5d7f86f44c5831b" | xxd -r -p | shasum -a 256Should print fe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "aae3dbfe1e75ecdb701a8693a80198ff7daad62daa02bb5a7061ee9a35094929" "fe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae" | xxd -r -p | shasum -a 256Should print 531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5" "f7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4" | xxd -r -p | shasum -a 256Should print fd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07
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/0x2838e247dcdc03d7e5d3def4582bb14c0fd666fbfbca325ed921536c8267f446The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification