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.

❤️ Your OB/GYN history may be part of your heart-health history

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

Stamp ID
STAMP-2026-1017-DF34AWSY
Content hash
045006797371dc7589db687c7daf0d311c270b8d882b652eac2b67970d5945e3
Day recorded
2026-10-17
Articles recorded that day
14
Attestation UID
0x954aae5491508351a76be05b38d4cef34ae05b9478cc1bee363f1de93bbf1681
View on EAS
Transaction
0x9c4640fb4dcea8118b9b300e3f91dc7e6f42de03d9e29eb50f4390ffdc328429
View on Basescan
Stamped
17 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0x02fe08efdccb71084a5770b417c0299b64f3bd30a4e0f543c976fa0f32296834

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
    0x07da0e1f7b47c71d9de587e0edc81b9b7df93ed7cb52575fea2ed1ca71201600
    0x385791b30c44fc3c8bb55eb0296a3e3aeaa77cc8cf0ce93c5ad8bb6dd601209e
  2. Step 2, combined with the value before it
    0x67e20324e52d44d9bdca2e3af9624e11c57ac5b65a3b95f08ab272e1d94628fc
    0x8d12ba429b23a7d1f9710a6095c3ce05fe826bd380f48bb60fe3257ae6e338b3
  3. Step 3, combined with the value before it
    0x243306bd12812188633ea86e0356bae8265333e85ea9c2ee24a015b3712c30e8
    0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

    This is the value for the whole day.

Value these steps arrive at
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

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
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa
Read from Base
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa
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":"Heart disease doesn’t suddenly begin at age 50 or 60. ","type":"text"}],"type":"…

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-1017-DF34AWSY/canonical" | shasum -a 256

    Should print 045006797371dc7589db687c7daf0d311c270b8d882b652eac2b67970d5945e3

  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-1017-DF34AWSY CONTENT=045006797371dc7589db687c7daf0d311c270b8d882b652eac2b67970d5945e3 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 02fe08efdccb71084a5770b417c0299b64f3bd30a4e0f543c976fa0f32296834

  3. 3. Combine step 1

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

    printf '01%s%s' "07da0e1f7b47c71d9de587e0edc81b9b7df93ed7cb52575fea2ed1ca71201600" "02fe08efdccb71084a5770b417c0299b64f3bd30a4e0f543c976fa0f32296834" | xxd -r -p | shasum -a 256

    Should print 385791b30c44fc3c8bb55eb0296a3e3aeaa77cc8cf0ce93c5ad8bb6dd601209e

  4. 4. Combine step 2

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

    printf '01%s%s' "67e20324e52d44d9bdca2e3af9624e11c57ac5b65a3b95f08ab272e1d94628fc" "385791b30c44fc3c8bb55eb0296a3e3aeaa77cc8cf0ce93c5ad8bb6dd601209e" | xxd -r -p | shasum -a 256

    Should print 8d12ba429b23a7d1f9710a6095c3ce05fe826bd380f48bb60fe3257ae6e338b3

  5. 5. Combine step 3

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

    printf '01%s%s' "243306bd12812188633ea86e0356bae8265333e85ea9c2ee24a015b3712c30e8" "8d12ba429b23a7d1f9710a6095c3ce05fe826bd380f48bb60fe3257ae6e338b3" | xxd -r -p | shasum -a 256

    Should print f100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

  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/0x954aae5491508351a76be05b38d4cef34ae05b9478cc1bee363f1de93bbf1681

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

Read the specification