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.

Clinical Trial Tracking: A SCAD Trial

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

Stamp ID
STAMP-2026-1006-Z6T5JD4F
Content hash
bb620f6791fa56096201e238f502311a2b06de8c9471f51b1b455dd910495a84
Day recorded
2026-10-06
Articles recorded that day
15
Attestation UID
0xa9df93f9287fa980c704294972498aa806fc4b33381236688843cf306b429249
View on EAS
Transaction
0xaa5931a912bc6fc948af848f821a21951d10120547c65c820efa653b1545aeeb
View on Basescan
Stamped
7 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

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

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
    0x6d7cfc6db4479e8cdd3659fc747860014dc3635be505e1ba02eae9ca0ebbffb8
    0x8849d97d1454717a5e8b759c86f355337194a53903bf0f1eff9ae6a6ab7beb53
  2. Step 2, combined with the value before it
    0x3f354da99cf8d9595d252baf1e6fe2a10cdff14b7992b02d975ab697294b89ce
    0xf6e9bee092ca40c02a96ef8ee26ca39530effb9351665feb3ba92e44033f0037
  3. Step 3, combined with the value before it
    0xa9f799966a483b5e226937bad04c452defeec34e6edcd62f9a25542551c7c5b8
    0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

    This is the value for the whole day.

Value these steps arrive at
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

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
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9
Read from Base
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9
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":"Clinical Trial Tracking: A SCAD Trial ","type":"text"}],"type":"paragraph"},{"co…

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-1006-Z6T5JD4F/canonical" | shasum -a 256

    Should print bb620f6791fa56096201e238f502311a2b06de8c9471f51b1b455dd910495a84

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

    Should print 6e96587150c61d201e29836b16e757b0a2da8b627f3f953d572de295831bda99

  3. 3. Combine step 1

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

    printf '01%s%s' "6d7cfc6db4479e8cdd3659fc747860014dc3635be505e1ba02eae9ca0ebbffb8" "6e96587150c61d201e29836b16e757b0a2da8b627f3f953d572de295831bda99" | xxd -r -p | shasum -a 256

    Should print 8849d97d1454717a5e8b759c86f355337194a53903bf0f1eff9ae6a6ab7beb53

  4. 4. Combine step 2

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

    printf '01%s%s' "3f354da99cf8d9595d252baf1e6fe2a10cdff14b7992b02d975ab697294b89ce" "8849d97d1454717a5e8b759c86f355337194a53903bf0f1eff9ae6a6ab7beb53" | xxd -r -p | shasum -a 256

    Should print f6e9bee092ca40c02a96ef8ee26ca39530effb9351665feb3ba92e44033f0037

  5. 5. Combine step 3

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

    printf '01%s%s' "a9f799966a483b5e226937bad04c452defeec34e6edcd62f9a25542551c7c5b8" "f6e9bee092ca40c02a96ef8ee26ca39530effb9351665feb3ba92e44033f0037" | xxd -r -p | shasum -a 256

    Should print 38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

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

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

Read the specification