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.

Diabetes Treatment Intensity and Accelerated Functional Decline in Older Adults: Evidence From the Health and Retirement Study

Zhang Wei, MS, Shuyang Fang, MD, Bing Yue, MD, Chayakrit Krittanawong, MD, FACC, FAHA, FSCAI, Erfan Darzi, PhD · 11 Nov 2026

Stamp ID
STAMP-2026-1111-3OP3AWV3
Content hash
e779c847a718ec29656e2e543556524f625c880cdafa510c07fb30d6a9c23d4f
Day recorded
2026-11-11
Articles recorded that day
10
Attestation UID
0x038df1af121af9057b7923fb09acbcb962e6eeca665243d0ece0bec7ac7a64cf
View on EAS
Transaction
0x04d028bf6563e888e37be9ee5affe94cb284be23dc6b64ec6bc1cc23b4319a68
View on Basescan
Stamped
11 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

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

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
    0xd1050cf56f53b4a4bdf0813b42eb102383a947e47af5231c2307142df4fcb975
    0xad881ec5cb53ac4ea134fdf21179104b6ac8e5a6889a32b744b330f050b09af2
  2. Step 2, combined with the value before it
    0xea4ac538576e50167cdab1bad1af89d1c32bbe2eb4433051ce9b9d61a1313f8b
    0x580fd2939109796f013d69c373b39cf4dc6fc69fe82151ff2cc2a1c0ff1c570e

    This is the value for the whole day.

Value these steps arrive at
0x580fd2939109796f013d69c373b39cf4dc6fc69fe82151ff2cc2a1c0ff1c570e

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
0x580fd2939109796f013d69c373b39cf4dc6fc69fe82151ff2cc2a1c0ff1c570e
Read from Base
0x580fd2939109796f013d69c373b39cf4dc6fc69fe82151ff2cc2a1c0ff1c570e
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":"Background: Functional limitation and disability are major consequences of diabetes in older adults. However, whether diabetes treatment intensity predicts accelerated functional decline beyond diabetes status alone remains unc…

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-1111-3OP3AWV3/canonical" | shasum -a 256

    Should print e779c847a718ec29656e2e543556524f625c880cdafa510c07fb30d6a9c23d4f

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

    Should print e162b573e12c62646847f1483a97b714afcdb8603bdef459ec2194f5d2eb16d6

  3. 3. Combine step 1

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

    printf '01%s%s' "d1050cf56f53b4a4bdf0813b42eb102383a947e47af5231c2307142df4fcb975" "e162b573e12c62646847f1483a97b714afcdb8603bdef459ec2194f5d2eb16d6" | xxd -r -p | shasum -a 256

    Should print ad881ec5cb53ac4ea134fdf21179104b6ac8e5a6889a32b744b330f050b09af2

  4. 4. Combine step 2

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

    printf '01%s%s' "ea4ac538576e50167cdab1bad1af89d1c32bbe2eb4433051ce9b9d61a1313f8b" "ad881ec5cb53ac4ea134fdf21179104b6ac8e5a6889a32b744b330f050b09af2" | xxd -r -p | shasum -a 256

    Should print 580fd2939109796f013d69c373b39cf4dc6fc69fe82151ff2cc2a1c0ff1c570e

  5. 5. 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/0x038df1af121af9057b7923fb09acbcb962e6eeca665243d0ece0bec7ac7a64cf

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

Read the specification