Verify

Sign inSign up

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.

🧬 GLP-1 Series: Lilly’s TRANSCEND-T2D-2 topline results

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

Stamp ID
STAMP-2026-1028-4SKSCUU6
Content hash
e26fcbd944d664a9a3d921950973d62740a24966b2bab5a235868dda3886713c
Day recorded
2026-10-29
Articles recorded that day
15
Attestation UID
0x8899fb532aaa534375a4265b9ae6bb33bcee855910a7de3906184684d2110e10
View on EAS
Transaction
0xd881d227c310a954059e99f66a3575b5f2fddf846abbd86f8b08e9c85f9deff5
View on Basescan
Stamped
29 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
0xfd04c2529373940d10d8867ced92664c2421517ad6f9bbbab77d172e9048d3da

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
    0x7ac59d848251a96c9df101dcea69f922f27882e039e480c18256563e74092270
    0x1c3df50faae6650ae10803c101987107d5a108ec72e7adffc9e86ac3f15c2ae7
  2. Step 2, combined with the value before it
    0x8684c972fb21792faae396237a29d162dea0c79122dc61b7e980cdfe7b7a5a11
    0x7ba59f79c485b8941758a3902291a85dbac5ba1aae8de8afc30d087f18e3ff70
  3. Step 3, combined with the value after it
    0xd4ebbe620cb382b8d20a214c89713da38e112a608a9072db1e972885426df50d
    0xa59fedf2908596b17a66f15c426b5f26270da19917b7f63f3be863d07885b414
  4. Step 4, combined with the value after it
    0xe867321f87a23a162dac7e6866d0e015ca57ed62f6ae8d180be1597532267975
    0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

    This is the value for the whole day.

Value these steps arrive at
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

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
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e
Read from Base
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e
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":"I’ve previously described Eli Lilly as the NVIDIA of healthcare.","type":"text"}…

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-1028-4SKSCUU6/canonical" | shasum -a 256

    Should print e26fcbd944d664a9a3d921950973d62740a24966b2bab5a235868dda3886713c

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

    Should print fd04c2529373940d10d8867ced92664c2421517ad6f9bbbab77d172e9048d3da

  3. 3. Combine step 1

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

    printf '01%s%s' "fd04c2529373940d10d8867ced92664c2421517ad6f9bbbab77d172e9048d3da" "7ac59d848251a96c9df101dcea69f922f27882e039e480c18256563e74092270" | xxd -r -p | shasum -a 256

    Should print 1c3df50faae6650ae10803c101987107d5a108ec72e7adffc9e86ac3f15c2ae7

  4. 4. Combine step 2

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

    printf '01%s%s' "8684c972fb21792faae396237a29d162dea0c79122dc61b7e980cdfe7b7a5a11" "1c3df50faae6650ae10803c101987107d5a108ec72e7adffc9e86ac3f15c2ae7" | xxd -r -p | shasum -a 256

    Should print 7ba59f79c485b8941758a3902291a85dbac5ba1aae8de8afc30d087f18e3ff70

  5. 5. Combine step 3

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

    printf '01%s%s' "7ba59f79c485b8941758a3902291a85dbac5ba1aae8de8afc30d087f18e3ff70" "d4ebbe620cb382b8d20a214c89713da38e112a608a9072db1e972885426df50d" | xxd -r -p | shasum -a 256

    Should print a59fedf2908596b17a66f15c426b5f26270da19917b7f63f3be863d07885b414

  6. 6. Combine step 4

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

    printf '01%s%s' "a59fedf2908596b17a66f15c426b5f26270da19917b7f63f3be863d07885b414" "e867321f87a23a162dac7e6866d0e015ca57ed62f6ae8d180be1597532267975" | xxd -r -p | shasum -a 256

    Should print 59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

  7. 7. 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/0x8899fb532aaa534375a4265b9ae6bb33bcee855910a7de3906184684d2110e10

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

Read the specification