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.

Would you let AI diagnose you?

Chayakrit Krittanawong, MD, FACC, FAHA, FSCAI · 4 Oct 2026

Stamp ID
STAMP-2026-1004-UFROBUMY
Content hash
3901778f40df1337ab7f296aa2731d2700772b17cf33c5227a718d0592caf9ee
Day recorded
2026-10-04
Articles recorded that day
18
Attestation UID
0xf6e9fba3ba6b1c6c69752bbc92919500502fb2928b7ae486ffe947b18c4abd7b
View on EAS
Transaction
0x22ca88a7c468bd5db1e7c0a5557a5c96ef85c6db922f1c80cc3508747dd1824d
View on Basescan
Stamped
4 Oct 2026

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
0x39afb49f9f7790af7d5ed31a8d24d6c4b415638123abbbfec50cc2038853e564

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 after it
    0x90b389db37f01cb57ed1a8ed8b9c3b72bd790d1ced0178ac641de285f706f891
    0x216bda84faad1a65f88feb948ad35688f37f31cccf0507ab5ad4a533c3656efc
  2. Step 2, combined with the value before it
    0x88a50bebd7946b0333cbc87ec0a580bef54324b77b7c68c0b3e83aede9bf5b95
    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
Read from Base
0x08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1
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,"agreement":false,"authors":[{"identity":"Drkrittanawong","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"This question suddenly feels a lot less hypothetical.","type":"text"}],"type":"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-1004-UFROBUMY/canonical" | shasum -a 256

    Should print 3901778f40df1337ab7f296aa2731d2700772b17cf33c5227a718d0592caf9ee

  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-1004-UFROBUMY CONTENT=3901778f40df1337ab7f296aa2731d2700772b17cf33c5227a718d0592caf9ee DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 39afb49f9f7790af7d5ed31a8d24d6c4b415638123abbbfec50cc2038853e564

  3. 3. Combine step 1

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

    printf '01%s%s' "39afb49f9f7790af7d5ed31a8d24d6c4b415638123abbbfec50cc2038853e564" "90b389db37f01cb57ed1a8ed8b9c3b72bd790d1ced0178ac641de285f706f891" | xxd -r -p | shasum -a 256

    Should print 216bda84faad1a65f88feb948ad35688f37f31cccf0507ab5ad4a533c3656efc

  4. 4. Combine step 2

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

    printf '01%s%s' "88a50bebd7946b0333cbc87ec0a580bef54324b77b7c68c0b3e83aede9bf5b95" "216bda84faad1a65f88feb948ad35688f37f31cccf0507ab5ad4a533c3656efc" | xxd -r -p | shasum -a 256

    Should print 08e365db5235a29439034a399eb9251c1f4830b35051a287fee77ba91b9fcbe1

  5. 5. 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/0xf6e9fba3ba6b1c6c69752bbc92919500502fb2928b7ae486ffe947b18c4abd7b

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

Read the specification