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-0911-T37DA63W Content hash 06e2f60e482ccb7970aff8fefaa12ddcc250ca436248b9b702cf0fafc8442eb7 Articles recorded that day 10 Attestation UID 0x0777f781c3114e7a308c1c456b362e473380e41b1d8c0ae13988ee4838cec2b6 View on EAS Transaction 0xf471f3a41bd42a59739e5da6862008bc1640a79c67497d308d570ce498765a5d 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 0xf9f77fe901b6641869bf4fc27bbcdbb358910f74e8e5cce9f16d9ffaef35fcd2 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 0x9603d2303939b64a4fc75a3b86a49813d3d4c33069016e4aec233b6eb25dbd2a 0x2b113749afb389f7322782b7b860e1d891c0f76de62fbd95a9fa2bdc42bd46c8 Step 2, combined with the value before it 0x725f0aca5eeec159be5e40f0fcf3fd9da2c3ed3e0b159cadbfea8c83bfae0fc7 0x66050a6b9d5b72b13b67015540818e2bea4b116ce8472643700d8884610d93fd Step 3, combined with the value before it 0x0f0e26a805d4361b929d81d81610e8441f025c15b2e2715e04b991a0e8d86877 0x61737b0f81bcd5ebe9984dd11b10d5bd6f9a93a9863770b7b855708a0e955bdb Step 4, combined with the value after it 0xe67227e12f7b6796a5da62c5b0b3e1dc6b226bfa012d15ca6736918c4e489e6f 0xc125bbd94e0c801e41e7822aa710f571e006056ce8ffba8003062a53720878a8 This is the value for the whole day.
Value these steps arrive at 0xc125bbd94e0c801e41e7822aa710f571e006056ce8ffba8003062a53720878a8 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 0xc125bbd94e0c801e41e7822aa710f571e006056ce8ffba8003062a53720878a8 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-0911-T37DA63W/canonical" | shasum -a 256Should print 06e2f60e482ccb7970aff8fefaa12ddcc250ca436248b9b702cf0fafc8442eb7
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-0911-T37DA63W
CONTENT=06e2f60e482ccb7970aff8fefaa12ddcc250ca436248b9b702cf0fafc8442eb7
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print f9f77fe901b6641869bf4fc27bbcdbb358910f74e8e5cce9f16d9ffaef35fcd2
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "9603d2303939b64a4fc75a3b86a49813d3d4c33069016e4aec233b6eb25dbd2a" "f9f77fe901b6641869bf4fc27bbcdbb358910f74e8e5cce9f16d9ffaef35fcd2" | xxd -r -p | shasum -a 256Should print 2b113749afb389f7322782b7b860e1d891c0f76de62fbd95a9fa2bdc42bd46c8
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "725f0aca5eeec159be5e40f0fcf3fd9da2c3ed3e0b159cadbfea8c83bfae0fc7" "2b113749afb389f7322782b7b860e1d891c0f76de62fbd95a9fa2bdc42bd46c8" | xxd -r -p | shasum -a 256Should print 66050a6b9d5b72b13b67015540818e2bea4b116ce8472643700d8884610d93fd
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "0f0e26a805d4361b929d81d81610e8441f025c15b2e2715e04b991a0e8d86877" "66050a6b9d5b72b13b67015540818e2bea4b116ce8472643700d8884610d93fd" | xxd -r -p | shasum -a 256Should print 61737b0f81bcd5ebe9984dd11b10d5bd6f9a93a9863770b7b855708a0e955bdb
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "61737b0f81bcd5ebe9984dd11b10d5bd6f9a93a9863770b7b855708a0e955bdb" "e67227e12f7b6796a5da62c5b0b3e1dc6b226bfa012d15ca6736918c4e489e6f" | xxd -r -p | shasum -a 256Should print c125bbd94e0c801e41e7822aa710f571e006056ce8ffba8003062a53720878a8
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/0x0777f781c3114e7a308c1c456b362e473380e41b1d8c0ae13988ee4838cec2b6The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification