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-0922-47BQEDIN Content hash bcedc2a95ced4d72b549279d9bf860f31c8551d66b98551f6f4a00cfd2bebd51 Articles recorded that day 19 Attestation UID 0x312f5bdaee9c1cd4c9c9e451ce2d932f82aa65985854eb05f9075f80314e1b63 View on EAS Transaction 0x54b4b79e498e2ec45d4be92b4c1c5b8f94b2c646cefaf982166895ba22ef85c1 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 18 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 0x7a0a1d9960ca1ac9981e1be0ffee9e3c2b9c3bcad30cd5899df4ba8ab68eebb3 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 0x6713667e1e40b0fa4b0be3eea49e931a5f899e7fc205cc95c33032139782a5f1 0xa748e82a617478f047116b988a268d33cedc40471a8ba59519691e44871a597f Step 2, combined with the value after it 0x29663d5cbac46f11005ce1e26e46533f33b487bc9e355638c960bf1b7855c205 0xee984bb7ff48aefe9c7e7da82ba0b8ae598afa7819c7fa982c47be37f5613bd4 Step 3, combined with the value after it 0x5ab3ad9ad20d8452ad1e5c597bfd6bccb3211f321fdd780431011cbfc90f1194 0x4be71e2b9fb83530c4a209f1bd3a792d9708748cfb7d4c6d07cad2bb9b0f9854 Step 4, combined with the value after it 0x3faa6df09366d7ee5ff95f70459f23ca502d10650176da7c4b4541197f2214d3 0xe63d808641c9100111b6b6585a9ed386e34c5f36ce79c50f14b6aaf0618b12fe Step 5, combined with the value after it 0x7a88f62292afb2658d20a5063a2b18d13343fa8e26ae33cb4daa3b0a0c688944 0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d This is the value for the whole day.
Value these steps arrive at 0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d 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 0x08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d 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.
{"abstract":null,"agreement":false,"authors":[{"identity":"90sTimeCapsule","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"Tamagatchi","src":"https://media.vitahash.org/articles/abccf150-454e-42e1-b438-0420f…Copy this text, paste it into any SHA-256 tool, and compare the result with the hash shown above. If the two match, this is exactly what Vitahash recorded.
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-0922-47BQEDIN/canonical" | shasum -a 256Should print bcedc2a95ced4d72b549279d9bf860f31c8551d66b98551f6f4a00cfd2bebd51
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-0922-47BQEDIN
CONTENT=bcedc2a95ced4d72b549279d9bf860f31c8551d66b98551f6f4a00cfd2bebd51
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 7a0a1d9960ca1ac9981e1be0ffee9e3c2b9c3bcad30cd5899df4ba8ab68eebb3
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "7a0a1d9960ca1ac9981e1be0ffee9e3c2b9c3bcad30cd5899df4ba8ab68eebb3" "6713667e1e40b0fa4b0be3eea49e931a5f899e7fc205cc95c33032139782a5f1" | xxd -r -p | shasum -a 256Should print a748e82a617478f047116b988a268d33cedc40471a8ba59519691e44871a597f
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "a748e82a617478f047116b988a268d33cedc40471a8ba59519691e44871a597f" "29663d5cbac46f11005ce1e26e46533f33b487bc9e355638c960bf1b7855c205" | xxd -r -p | shasum -a 256Should print ee984bb7ff48aefe9c7e7da82ba0b8ae598afa7819c7fa982c47be37f5613bd4
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "ee984bb7ff48aefe9c7e7da82ba0b8ae598afa7819c7fa982c47be37f5613bd4" "5ab3ad9ad20d8452ad1e5c597bfd6bccb3211f321fdd780431011cbfc90f1194" | xxd -r -p | shasum -a 256Should print 4be71e2b9fb83530c4a209f1bd3a792d9708748cfb7d4c6d07cad2bb9b0f9854
6. Combine step 4 The value you have goes first, then the published value.
printf '01%s%s' "4be71e2b9fb83530c4a209f1bd3a792d9708748cfb7d4c6d07cad2bb9b0f9854" "3faa6df09366d7ee5ff95f70459f23ca502d10650176da7c4b4541197f2214d3" | xxd -r -p | shasum -a 256Should print e63d808641c9100111b6b6585a9ed386e34c5f36ce79c50f14b6aaf0618b12fe
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "e63d808641c9100111b6b6585a9ed386e34c5f36ce79c50f14b6aaf0618b12fe" "7a88f62292afb2658d20a5063a2b18d13343fa8e26ae33cb4daa3b0a0c688944" | xxd -r -p | shasum -a 256Should print 08de2d0ad5fb90d3e053eb878d60fbda4d2fb97afd72ecdf81de0214801fd41d
8. 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/0x312f5bdaee9c1cd4c9c9e451ce2d932f82aa65985854eb05f9075f80314e1b63The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification