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-0929-NL7GJJFS Content hash 4b560088b2ee7cf89020f5c5a5e0e51818c384c9160aa9fa9ab85ca4fc8a8af9 Articles recorded that day 14 Attestation UID 0xa1006c6226d4a015bffa7fddabd4db5db8582a79a901a0ea1835c5a72e3fd109 View on EAS Transaction 0xa625137b61bde7a2c0cfe8bf2d04a487d36f731ff5eb385b52213075de54c776 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 13 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 0x6a0e0d07fdf2c6a006ec2e240f2876e22e6fa9e5f66eeab6be17f506e6f6adb1 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 0x9a4e6e7b768acf60670aabe7ccd896a66714d60b974a63e19d54ea80acbd1ef2 0xf52a332ed3eabffdfbf8f136c95bc25fdd8c7380933fccaad2d56a8388ad3a15 Step 2, combined with the value before it 0x2dd26d058fe6b986bc3c2f924902c4d5121205247cfa46698ecbfa4e241ec843 0x792d513ef76d0c30816e13b375c164b85fba386b36c8727295bd62a32ab6fc0e Step 3, combined with the value before it 0x64b372d3b8b7ce059ee610f05db948d18b4ad52db869c1da5e5d7eae3fc6e143 0xe9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9 Step 4, combined with the value after it 0x9839c50d956d1a2897706be0b518a912ccfac8b30716781f1f871dc7e09c56de 0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4 This is the value for the whole day.
Value these steps arrive at 0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4 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 0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4 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-0929-NL7GJJFS/canonical" | shasum -a 256Should print 4b560088b2ee7cf89020f5c5a5e0e51818c384c9160aa9fa9ab85ca4fc8a8af9
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-0929-NL7GJJFS
CONTENT=4b560088b2ee7cf89020f5c5a5e0e51818c384c9160aa9fa9ab85ca4fc8a8af9
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 6a0e0d07fdf2c6a006ec2e240f2876e22e6fa9e5f66eeab6be17f506e6f6adb1
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "6a0e0d07fdf2c6a006ec2e240f2876e22e6fa9e5f66eeab6be17f506e6f6adb1" "9a4e6e7b768acf60670aabe7ccd896a66714d60b974a63e19d54ea80acbd1ef2" | xxd -r -p | shasum -a 256Should print f52a332ed3eabffdfbf8f136c95bc25fdd8c7380933fccaad2d56a8388ad3a15
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "2dd26d058fe6b986bc3c2f924902c4d5121205247cfa46698ecbfa4e241ec843" "f52a332ed3eabffdfbf8f136c95bc25fdd8c7380933fccaad2d56a8388ad3a15" | xxd -r -p | shasum -a 256Should print 792d513ef76d0c30816e13b375c164b85fba386b36c8727295bd62a32ab6fc0e
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "64b372d3b8b7ce059ee610f05db948d18b4ad52db869c1da5e5d7eae3fc6e143" "792d513ef76d0c30816e13b375c164b85fba386b36c8727295bd62a32ab6fc0e" | xxd -r -p | shasum -a 256Should print e9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "e9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9" "9839c50d956d1a2897706be0b518a912ccfac8b30716781f1f871dc7e09c56de" | xxd -r -p | shasum -a 256Should print 0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4
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/0xa1006c6226d4a015bffa7fddabd4db5db8582a79a901a0ea1835c5a72e3fd109The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification