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.

🚨 Familial Hypercholesterolemia (FH): Don’t Miss It

Chayakrit Krittanawong, MD, FACC, FSCAI · 9 Sept 2026

Stamp ID
STAMP-2026-0909-5Q3VXU77
Content hash
750b15ec5aa48f0539702c06673ad99034c3814ffe54bfc1f67d80ab7566977f
Day recorded
2026-09-09
Articles recorded that day
5
Attestation UID
0x041787fece6c3c97abcdbdfd65d43fd8125061a1f4e92a7f5c47448ecdc8af04
View on EAS
Transaction
0xd71488576af19f7a6acb3cc7cb24389b2387be4a2954deaab8ebbf837587d546
View on Basescan
Stamped
9 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 4 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
0x573d97052f719372b975126cbc095b8b87b25f2d3c8af808a84d41a3ec9a2265

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
    0xa9ef9d14af2276045db23fb862163a459156988b9ef9e47a3ec7d6f6d96e91c9
    0x8a9e14acf6fe0c47f83b59044352044477b85f139fb9df4efb8df3166759691d
  2. Step 2, combined with the value before it
    0xc06d3d56f4fff8ede166ce30e481a37cd1599bced0921dec2ba234be914bba86
    0xc0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07
  3. Step 3, combined with the value after it
    0x1b30e5f2d6a413c35cae4be57ffcb0f83ac838f84cc8e682af6a227dfeace9a9
    0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

    This is the value for the whole day.

Value these steps arrive at
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

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
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789
Read from Base
0x23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789
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":"Drkrittanawong","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"What if your “high cholesterol” isn’t just about your diet?","type":"text"},{"type":"hardBreak"},{…

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-0909-5Q3VXU77/canonical" | shasum -a 256

    Should print 750b15ec5aa48f0539702c06673ad99034c3814ffe54bfc1f67d80ab7566977f

  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-0909-5Q3VXU77 CONTENT=750b15ec5aa48f0539702c06673ad99034c3814ffe54bfc1f67d80ab7566977f DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 573d97052f719372b975126cbc095b8b87b25f2d3c8af808a84d41a3ec9a2265

  3. 3. Combine step 1

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

    printf '01%s%s' "a9ef9d14af2276045db23fb862163a459156988b9ef9e47a3ec7d6f6d96e91c9" "573d97052f719372b975126cbc095b8b87b25f2d3c8af808a84d41a3ec9a2265" | xxd -r -p | shasum -a 256

    Should print 8a9e14acf6fe0c47f83b59044352044477b85f139fb9df4efb8df3166759691d

  4. 4. Combine step 2

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

    printf '01%s%s' "c06d3d56f4fff8ede166ce30e481a37cd1599bced0921dec2ba234be914bba86" "8a9e14acf6fe0c47f83b59044352044477b85f139fb9df4efb8df3166759691d" | xxd -r -p | shasum -a 256

    Should print c0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07

  5. 5. Combine step 3

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

    printf '01%s%s' "c0eb5b9d3eff694e69f590bdf1c8e7b36646323f2e99099db557d9a9ece7da07" "1b30e5f2d6a413c35cae4be57ffcb0f83ac838f84cc8e682af6a227dfeace9a9" | xxd -r -p | shasum -a 256

    Should print 23b3eacc7f982828bd99a6eb6700f18b9ee256884eaea95068e33ee081173789

  6. 6. 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/0x041787fece6c3c97abcdbdfd65d43fd8125061a1f4e92a7f5c47448ecdc8af04

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

Read the specification