Verify

Verified on Base

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-0820-J43AUBMU
Content hash
cbdc5a06d4337ec608df63fdcb28ae98a5d725f8a4d7f9ca86f922c3e481bdfa
Day recorded
2026-08-21
Articles recorded that day
2
Attestation UID
0xbe97cf7e5245ab04475fa8df60a3b14a0e087906f24a0fdeaba5c0418ec449a2
View on EAS
Transaction
0x8b928b8d9cbe6eca8b78b5a2c770a01f9547dc386359ebdf58e2f5de6e71f9b0
View on Basescan
Stamped
21 Aug 2026

Recorded on Base Sepolia using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other article 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
0x1a9e5736a25dc78e7cfe2f4a311b224a06b8bc5c4913e11548fc57f058da5d71

Built from this article's content hash and its stamp ID, as sha256(0x00 || sha256(utf8(stampId)) || contentHash).

  1. Step 1, combined with the value before it
    0xf153925d05fc1cc2d3b01c5ab25058f4f991147e3e54cb387e8858da844fa567
    0x52cf934a1dd118c595762f18cd7b6ed038b782e662eb3d518baa25c765fa40e7

    This is the value for the whole day.

Value these steps arrive at
0x52cf934a1dd118c595762f18cd7b6ed038b782e662eb3d518baa25c765fa40e7

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
0x52cf934a1dd118c595762f18cd7b6ed038b782e662eb3d518baa25c765fa40e7
Read from Base
0x52cf934a1dd118c595762f18cd7b6ed038b782e662eb3d518baa25c765fa40e7
Read it yourself on EAS

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,"authors":[{"identity":"cardiovitahash","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Cardiology pearl 🫀","type":"text"}],"type":"paragraph"},{"content":[{"text":"A \"silent\" MI can p…

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.

For a technical reader: the terminal route
  1. 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-0820-J43AUBMU/canonical" | shasum -a 256

    Should print cbdc5a06d4337ec608df63fdcb28ae98a5d725f8a4d7f9ca86f922c3e481bdfa

  2. 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-0820-J43AUBMU CONTENT=cbdc5a06d4337ec608df63fdcb28ae98a5d725f8a4d7f9ca86f922c3e481bdfa DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 1a9e5736a25dc78e7cfe2f4a311b224a06b8bc5c4913e11548fc57f058da5d71

  3. 3. Combine step 1

    The published value goes first, then the value you have.

    printf '01%s%s' "f153925d05fc1cc2d3b01c5ab25058f4f991147e3e54cb387e8858da844fa567" "1a9e5736a25dc78e7cfe2f4a311b224a06b8bc5c4913e11548fc57f058da5d71" | xxd -r -p | shasum -a 256

    Should print 52cf934a1dd118c595762f18cd7b6ed038b782e662eb3d518baa25c765fa40e7

  4. 4. 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-sepolia.easscan.org/attestation/view/0xbe97cf7e5245ab04475fa8df60a3b14a0e087906f24a0fdeaba5c0418ec449a2

The rules these commands follow are written down in full, so anyone can reimplement them.

Read the specification