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-1009-KKDZPDSI Content hash 59752b068466e1472fda3e7458180b299c3fa90403facc38e5987c711d3f3245 Articles recorded that day 19 Attestation UID 0xb5876e55d95e5c9dd72430517b418d7e00db9efadd7c258e2a99bed5d50d278b View on EAS Transaction 0xdb7e81090abd4ba966e61ef8e62756a94bcf19b7c809c51e90b31991e1231c26 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 0xae24b1ca1b828f19e8941a24c2b98951608329840c1bd9f16a134b85d61ef9b7 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 0xa59a020f41a83908b2e7e5c81e0b1ae406fd0feffcb10f8b8e95eaba278782f6 0xf7187a57ca6819ea24cb35da8bfe317f6afb09a8b390b8d7a3d01abcb4e59649 Step 2, combined with the value after it 0xfb1fce5e47a1a7690a878e3357df58753baa5d1a1e310cac1c8e9fa76089e1e9 0xe82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8 Step 3, combined with the value after it 0x9544434adc4bff681dabbe85f0bed8127c8ebc681826cd5b6a618d47b1a3a76c 0x2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d Step 4, combined with the value before it 0x2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d 0xfe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac Step 5, combined with the value after it 0x180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f 0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68 This is the value for the whole day.
Value these steps arrive at 0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68 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 0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68 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":"simple_recipes_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"Sweet Potato Casserole","src":"https://media.vitahash.org/articles/94bc321a-18…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-1009-KKDZPDSI/canonical" | shasum -a 256Should print 59752b068466e1472fda3e7458180b299c3fa90403facc38e5987c711d3f3245
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-1009-KKDZPDSI
CONTENT=59752b068466e1472fda3e7458180b299c3fa90403facc38e5987c711d3f3245
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print ae24b1ca1b828f19e8941a24c2b98951608329840c1bd9f16a134b85d61ef9b7
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "ae24b1ca1b828f19e8941a24c2b98951608329840c1bd9f16a134b85d61ef9b7" "a59a020f41a83908b2e7e5c81e0b1ae406fd0feffcb10f8b8e95eaba278782f6" | xxd -r -p | shasum -a 256Should print f7187a57ca6819ea24cb35da8bfe317f6afb09a8b390b8d7a3d01abcb4e59649
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "f7187a57ca6819ea24cb35da8bfe317f6afb09a8b390b8d7a3d01abcb4e59649" "fb1fce5e47a1a7690a878e3357df58753baa5d1a1e310cac1c8e9fa76089e1e9" | xxd -r -p | shasum -a 256Should print e82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "e82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8" "9544434adc4bff681dabbe85f0bed8127c8ebc681826cd5b6a618d47b1a3a76c" | xxd -r -p | shasum -a 256Should print 2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d" "2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d" | xxd -r -p | shasum -a 256Should print fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac" "180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f" | xxd -r -p | shasum -a 256Should print 828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68
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/0xb5876e55d95e5c9dd72430517b418d7e00db9efadd7c258e2a99bed5d50d278bThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification