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-0927-HJRXF7XA Content hash 38405b0f4364881f46791fd773e971ccb43de05585bc883b702e6d2f878c7870 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 0x49e562d6bf13b9744ec0458ce5dc990061dab0df0484a0abb18793812d4e6f21 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 0xf8498d12d3dff0ca9532fde03597ab06d331a906d17799eef1162f081a9dc88e 0x2c3bcdc269a6af49f9fc91560ea294bee65a7a96cb7d37f45d70a99c80a40ec6 Step 2, combined with the value after it 0x27b3ca228b1115946ab4f7bed4bfa4015e18afecb6e06c7933b61a52b6d543fb 0xaa578ddfcefd3ad1326c523a92417afa15727ca3825ec5b50289ac1d7e795dc3 Step 3, combined with the value before it 0x7fe40eea1bad2bdb93609aa8e573a82f09091eb8006a6e0767682226d1a75fe1 0x6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73 Step 4, combined with the value after it 0x189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e 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-0927-HJRXF7XA/canonical" | shasum -a 256Should print 38405b0f4364881f46791fd773e971ccb43de05585bc883b702e6d2f878c7870
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-0927-HJRXF7XA
CONTENT=38405b0f4364881f46791fd773e971ccb43de05585bc883b702e6d2f878c7870
DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1)
printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256Should print 49e562d6bf13b9744ec0458ce5dc990061dab0df0484a0abb18793812d4e6f21
3. Combine step 1 The value you have goes first, then the published value.
printf '01%s%s' "49e562d6bf13b9744ec0458ce5dc990061dab0df0484a0abb18793812d4e6f21" "f8498d12d3dff0ca9532fde03597ab06d331a906d17799eef1162f081a9dc88e" | xxd -r -p | shasum -a 256Should print 2c3bcdc269a6af49f9fc91560ea294bee65a7a96cb7d37f45d70a99c80a40ec6
4. Combine step 2 The value you have goes first, then the published value.
printf '01%s%s' "2c3bcdc269a6af49f9fc91560ea294bee65a7a96cb7d37f45d70a99c80a40ec6" "27b3ca228b1115946ab4f7bed4bfa4015e18afecb6e06c7933b61a52b6d543fb" | xxd -r -p | shasum -a 256Should print aa578ddfcefd3ad1326c523a92417afa15727ca3825ec5b50289ac1d7e795dc3
5. Combine step 3 The published value goes first, then the value you have.
printf '01%s%s' "7fe40eea1bad2bdb93609aa8e573a82f09091eb8006a6e0767682226d1a75fe1" "aa578ddfcefd3ad1326c523a92417afa15727ca3825ec5b50289ac1d7e795dc3" | xxd -r -p | shasum -a 256Should print 6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73
6. Combine step 4 The value you have goes first, then the published value.
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