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-1003-W62VPLTD Content hash ccc998dc530edb6c7097fa5a8e837f83a6128eb9ac94c25bb3ae00b807fe7c14 Articles recorded that day 18 Attestation UID 0xf6e9fba3ba6b1c6c69752bbc92919500502fb2928b7ae486ffe947b18c4abd7b View on EAS Transaction 0x22ca88a7c468bd5db1e7c0a5557a5c96ef85c6db922f1c80cc3508747dd1824d 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 17 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 0x39357dfa61f4c43c42e752ffbece24980eb3a5b685cbd35b8c6768e2f6f175ca 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 0xc73d8439313b2b3012a66e08f18eeb33c5bd643ce7eb1f6142d5b43b20b7bf44 0xb3d860690ca2ffb3b982633d5861982ffd7dfd6394a6079666018c58e2eda1ce Step 2, combined with the value before it 0x9899cd4ae99e95834e958d8bb897a7af91808f9275e50c6b15f7cad098813700 0x32f4b79e7ce088036f1b7c413bf5e730a6c3e378101a0ec5120faecdf370f6a1 Step 3, combined with the value after it 0xb4a683662da217fb9a073ac28d7879f63f863d681c983f0acede4f8eb4cfc4e4 0x6084880ccb9031ec74fb9ebfcad8c7d373e8fe72a594da8699dcaec3990083df Step 4, combined with the value before it 0xf06af4023575444307257bc7eb7d2206954e59673b7705a6aaa0edbad5a1fdef 0x88a50bebd7946b0333cbc87ec0a580bef54324b77b7c68c0b3e83aede9bf5b95 Step 5, combined with the value after it 0x216bda84faad1a65f88feb948ad35688f37f31cccf0507ab5ad4a533c3656efc 0x08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1 This is the value for the whole day.
Value these steps arrive at 0x08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1 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 0x08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1 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":[{"content":[{"text":"Prep time: 15 minutes | Chill time: 3–4 hours","type":"text"}],"type":"par…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-1003-W62VPLTD/canonical" | shasum -a 256Should print ccc998dc530edb6c7097fa5a8e837f83a6128eb9ac94c25bb3ae00b807fe7c14
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-1003-W62VPLTD
CONTENT=ccc998dc530edb6c7097fa5a8e837f83a6128eb9ac94c25bb3ae00b807fe7c14
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 39357dfa61f4c43c42e752ffbece24980eb3a5b685cbd35b8c6768e2f6f175ca
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "c73d8439313b2b3012a66e08f18eeb33c5bd643ce7eb1f6142d5b43b20b7bf44" "39357dfa61f4c43c42e752ffbece24980eb3a5b685cbd35b8c6768e2f6f175ca" | xxd -r -p | shasum -a 256Should print b3d860690ca2ffb3b982633d5861982ffd7dfd6394a6079666018c58e2eda1ce
4. Combine step 2 The published value goes first, then the value you have.
printf '01%s%s' "9899cd4ae99e95834e958d8bb897a7af91808f9275e50c6b15f7cad098813700" "b3d860690ca2ffb3b982633d5861982ffd7dfd6394a6079666018c58e2eda1ce" | xxd -r -p | shasum -a 256Should print 32f4b79e7ce088036f1b7c413bf5e730a6c3e378101a0ec5120faecdf370f6a1
5. Combine step 3 The value you have goes first, then the published value.
printf '01%s%s' "32f4b79e7ce088036f1b7c413bf5e730a6c3e378101a0ec5120faecdf370f6a1" "b4a683662da217fb9a073ac28d7879f63f863d681c983f0acede4f8eb4cfc4e4" | xxd -r -p | shasum -a 256Should print 6084880ccb9031ec74fb9ebfcad8c7d373e8fe72a594da8699dcaec3990083df
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "f06af4023575444307257bc7eb7d2206954e59673b7705a6aaa0edbad5a1fdef" "6084880ccb9031ec74fb9ebfcad8c7d373e8fe72a594da8699dcaec3990083df" | xxd -r -p | shasum -a 256Should print 88a50bebd7946b0333cbc87ec0a580bef54324b77b7c68c0b3e83aede9bf5b95
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "88a50bebd7946b0333cbc87ec0a580bef54324b77b7c68c0b3e83aede9bf5b95" "216bda84faad1a65f88feb948ad35688f37f31cccf0507ab5ad4a533c3656efc" | xxd -r -p | shasum -a 256Should print 08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1
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/0xf6e9fba3ba6b1c6c69752bbc92919500502fb2928b7ae486ffe947b18c4abd7bThe rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification