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-0919-S54YCAG4 Content hash 7b674166f82969c2c6dba80cc9b31ba136a597f8754416441c34d8d9b1b218e9 Articles recorded that day 18 Attestation UID 0x1ed0b640723183fed258fb97c6562ff95da0496d1406e14653e12c062865f9d3 View on EAS Transaction 0x7b9fdc49a1760db010f3985639be208da0d433b5b3f9fa84e64abdaa135d36d6 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 0xa82754f52aac3ece5021754dece736a2ae71886a1d25839af4bfb8d5b9954c5c 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 0x70de333bf334383da6c09f38a0b87b556039a5038ed325ab1c8c18afea1e3436 0xd07f3474201006c6793e8c09e459a80fc715b11d0fa10a65e2128646045a6eea Step 2, combined with the value after it 0x32a59bef16ddb68b945968492d91ce9135516eabe7ffd0a53e0d4412fa3c38d4 0xdfe86050bde6474cfac0f473484524caab9066cb2c189566cfe3a79de76390b1 Step 3, combined with the value before it 0x4c4970dd96aad6ebb5840b1c36e099ec5e477a60e21b738c1f75ecf72dd79fdb 0x88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3 Step 4, combined with the value before it 0x6ddc36faf65fa6578b988653de332a1f027710b88843c4a0b1ff15f7b542a8ed 0x55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567 Step 5, combined with the value after it 0x2544de35a4de67f9861a894e1a2eed77c03547acb509e6b8af67a233143738ac 0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997 This is the value for the whole day.
Value these steps arrive at 0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997 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 0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997 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-0919-S54YCAG4/canonical" | shasum -a 256Should print 7b674166f82969c2c6dba80cc9b31ba136a597f8754416441c34d8d9b1b218e9
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-0919-S54YCAG4
CONTENT=7b674166f82969c2c6dba80cc9b31ba136a597f8754416441c34d8d9b1b218e9
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print a82754f52aac3ece5021754dece736a2ae71886a1d25839af4bfb8d5b9954c5c
3. Combine step 1 The published value goes first, then the value you have.
printf '01%s%s' "70de333bf334383da6c09f38a0b87b556039a5038ed325ab1c8c18afea1e3436" "a82754f52aac3ece5021754dece736a2ae71886a1d25839af4bfb8d5b9954c5c" | xxd -r -p | shasum -a 256Should print d07f3474201006c6793e8c09e459a80fc715b11d0fa10a65e2128646045a6eea
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "d07f3474201006c6793e8c09e459a80fc715b11d0fa10a65e2128646045a6eea" "32a59bef16ddb68b945968492d91ce9135516eabe7ffd0a53e0d4412fa3c38d4" | xxd -r -p | shasum -a 256Should print dfe86050bde6474cfac0f473484524caab9066cb2c189566cfe3a79de76390b1
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "4c4970dd96aad6ebb5840b1c36e099ec5e477a60e21b738c1f75ecf72dd79fdb" "dfe86050bde6474cfac0f473484524caab9066cb2c189566cfe3a79de76390b1" | xxd -r -p | shasum -a 256Should print 88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3
6. Combine step 4 The published value goes first, then the value you have.
printf '01%s%s' "6ddc36faf65fa6578b988653de332a1f027710b88843c4a0b1ff15f7b542a8ed" "88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3" | xxd -r -p | shasum -a 256Should print 55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567
7. Combine step 5 The value you have goes first, then the published value.
printf '01%s%s' "55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567" "2544de35a4de67f9861a894e1a2eed77c03547acb509e6b8af67a233143738ac" | xxd -r -p | shasum -a 256Should print 604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997
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/0x1ed0b640723183fed258fb97c6562ff95da0496d1406e14653e12c062865f9d3The rules these commands follow are written down in full, so anyone can reimplement them.
Read the specification