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-0928-ZRXMUXXJ Content hash 03ccc7346ee2ebf28628dda11ccd5d5b0af1fe6b545e2350dd89373c7a1fca86 Articles recorded that day 16 Attestation UID 0xf90e9bc451eee5367128ecc6c707fc5352ef0515b57dec1f5af014911dd29347 View on EAS Transaction 0x0f2874f7536c4d6526c65e0119f22d2ba40a142cf577fc5ab655a4834d402d41 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 0x1d6b7446b9918271f74f8e6de0f53aebe66e565cf59b5f11528f6f3c4786d1c2 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 0xf077a7982be0c24f17b319304ef50ae6604d51d7ff89d551c0d35041999ea381 0xf2e28bae3cabd4b3648a42dc6a3a87b4132e8d1be48fc43872ebbd3a3617574f Step 2, combined with the value before it 0x5d1c7bfd843242f2ad1fe89866ca257f29e5bf47a9c54c525d7f6c19a534edd5 0x38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20 Step 3, combined with the value before it 0xd3c2f94c5c767cdb10be31c6ddf7bc5882f37bdff20906c367194ada68ba2524 0x189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e Step 4, combined with the value before it 0x6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73 0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94 This is the value for the whole day.
Value these steps arrive at 0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94 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 0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94 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-0928-ZRXMUXXJ/canonical" | shasum -a 256Should print 03ccc7346ee2ebf28628dda11ccd5d5b0af1fe6b545e2350dd89373c7a1fca86
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-0928-ZRXMUXXJ
CONTENT=03ccc7346ee2ebf28628dda11ccd5d5b0af1fe6b545e2350dd89373c7a1fca86
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 1d6b7446b9918271f74f8e6de0f53aebe66e565cf59b5f11528f6f3c4786d1c2
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "f077a7982be0c24f17b319304ef50ae6604d51d7ff89d551c0d35041999ea381" "1d6b7446b9918271f74f8e6de0f53aebe66e565cf59b5f11528f6f3c4786d1c2" | xxd -r -p | shasum -a 256Should print f2e28bae3cabd4b3648a42dc6a3a87b4132e8d1be48fc43872ebbd3a3617574f
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "5d1c7bfd843242f2ad1fe89866ca257f29e5bf47a9c54c525d7f6c19a534edd5" "f2e28bae3cabd4b3648a42dc6a3a87b4132e8d1be48fc43872ebbd3a3617574f" | xxd -r -p | shasum -a 256Should print 38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "d3c2f94c5c767cdb10be31c6ddf7bc5882f37bdff20906c367194ada68ba2524" "38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20" | xxd -r -p | shasum -a 256Should print 189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73" "189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e" | xxd -r -p | shasum -a 256Should print 01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94
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/0xf90e9bc451eee5367128ecc6c707fc5352ef0515b57dec1f5af014911dd29347The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification