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.

Toward Transparent AI Disclosure in Medical Publishing: A Proposed Clinical AI Score Framework

Chayakrit Krittanawong, MD, FACC, FAHA, FSCAI · 10 Sept 2026

Stamp ID
STAMP-2026-0910-5NCUY2J7
Content hash
706a31156ca87cd941e84f8d142b1be8eca2c5a840fdaed03c2109ebc2e3896b
Day recorded
2026-09-10
Articles recorded that day
8
Attestation UID
0xf8f0e64849d3ba6f01e8709c90250a8b400b96bd9576e39e7949fa6c0043408b
View on EAS
Transaction
0x74e43b2e9ba0b4a17a30a17cd69341ab9f4af4cebcdb4747b7188b0b5e486d70
View on Basescan
Stamped
10 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

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

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
    0xa2ba057a8c42780133beacced76e75881f219f151d50157b39f2dfd3f0982eef
    0xfacfea826e85751fb7165e01c0d0926d94cd991d236e1900c5aff4ba2574aea7
  2. Step 2, combined with the value before it
    0xb6bbedcf5392a6c93eeb861d134575755aa24767dbaa5f68c31a0a4b496717d3
    0x017a0ea40754398dd234718206ec2e41b1a8edbba60ed294acb0d81580cdbd00
  3. Step 3, combined with the value before it
    0x97af53e90c4e942303167c11b3028a112931ba0b2216464cdd9d2eafcea2a2a1
    0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

    This is the value for the whole day.

Value these steps arrive at
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

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
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048
Read from Base
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048
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.

The exact text is not available for this article right now. The command below still reaches it.

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-0910-5NCUY2J7/canonical" | shasum -a 256

    Should print 706a31156ca87cd941e84f8d142b1be8eca2c5a840fdaed03c2109ebc2e3896b

  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-0910-5NCUY2J7 CONTENT=706a31156ca87cd941e84f8d142b1be8eca2c5a840fdaed03c2109ebc2e3896b DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 03b967524d01933c88901a755f94669e94b83ab5b674502a28675083c44b8317

  3. 3. Combine step 1

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

    printf '01%s%s' "03b967524d01933c88901a755f94669e94b83ab5b674502a28675083c44b8317" "a2ba057a8c42780133beacced76e75881f219f151d50157b39f2dfd3f0982eef" | xxd -r -p | shasum -a 256

    Should print facfea826e85751fb7165e01c0d0926d94cd991d236e1900c5aff4ba2574aea7

  4. 4. Combine step 2

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

    printf '01%s%s' "b6bbedcf5392a6c93eeb861d134575755aa24767dbaa5f68c31a0a4b496717d3" "facfea826e85751fb7165e01c0d0926d94cd991d236e1900c5aff4ba2574aea7" | xxd -r -p | shasum -a 256

    Should print 017a0ea40754398dd234718206ec2e41b1a8edbba60ed294acb0d81580cdbd00

  5. 5. Combine step 3

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

    printf '01%s%s' "97af53e90c4e942303167c11b3028a112931ba0b2216464cdd9d2eafcea2a2a1" "017a0ea40754398dd234718206ec2e41b1a8edbba60ed294acb0d81580cdbd00" | xxd -r -p | shasum -a 256

    Should print b7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

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

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

Read the specification