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.

☕ Can coffee help protect the brain?

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

Stamp ID
STAMP-2026-1024-TS554OXY
Content hash
9c3d16f62af7f6a9e11e73847b010310a714c843c2ea67212bc7fd2b73df8b6c
Day recorded
2026-10-24
Articles recorded that day
17
Attestation UID
0x99ce65ad3e3a0d7d4e90e274691f2ed402696c16d0feac0a1c0e5793bbe9bb06
View on EAS
Transaction
0x80c40265258b1fc12f44726cd8cd1aeb5beb0fb4795a5f29bd1b1a262efdc455
View on Basescan
Stamped
24 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

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

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
    0x294c2d2462b00e0caacdc624d367f39cee7916cc004b010afc6ec9a1ea703563
    0x3b6d88d28a3e4e712f67afb6558b84bbe655b65b23c97aa3d08350831c29f0d2
  2. Step 2, combined with the value before it
    0x2dde2715cbc674d1ef879632448cb5eeb6a5d444cb6ba98869e786ba555db650
    0xe11551e1c82e2844519f84ed3249d1844c83f2304a7ff09f3715329a8ddf246a
  3. Step 3, combined with the value before it
    0x7b7afb342e521901bc3203dcfc02476d8a86c344d98b10ea9135817edcc00fce
    0x9b61f652517d4d78b2619906032bed4a793cfb94cd760aead9f10ceb908d2f8f
  4. Step 4, combined with the value before it
    0x98c37ce05d3b44441f0601a06f3b1d844fc63cbc305e7e35908bc303ceeb0659
    0x3a5afcf84a1bf5e336bff4d34c03792ed24edc9df5a5bbc68ade80222f91d6ed
  5. Step 5, combined with the value after it
    0x68f69fa84996c11465daa44ab990c45da47c0bc64ebea34ad51180cd9223a4cf
    0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

    This is the value for the whole day.

Value these steps arrive at
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

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
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9
Read from Base
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9
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":"A 2026 JAMA study followed 131,821 people for up to 43 years, documenting 11,033…

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-1024-TS554OXY/canonical" | shasum -a 256

    Should print 9c3d16f62af7f6a9e11e73847b010310a714c843c2ea67212bc7fd2b73df8b6c

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

    Should print 215fcbb3ace30d51e6fc9cb84d2e4f1f806ba008e454cd13d9d30b2c46181079

  3. 3. Combine step 1

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

    printf '01%s%s' "294c2d2462b00e0caacdc624d367f39cee7916cc004b010afc6ec9a1ea703563" "215fcbb3ace30d51e6fc9cb84d2e4f1f806ba008e454cd13d9d30b2c46181079" | xxd -r -p | shasum -a 256

    Should print 3b6d88d28a3e4e712f67afb6558b84bbe655b65b23c97aa3d08350831c29f0d2

  4. 4. Combine step 2

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

    printf '01%s%s' "2dde2715cbc674d1ef879632448cb5eeb6a5d444cb6ba98869e786ba555db650" "3b6d88d28a3e4e712f67afb6558b84bbe655b65b23c97aa3d08350831c29f0d2" | xxd -r -p | shasum -a 256

    Should print e11551e1c82e2844519f84ed3249d1844c83f2304a7ff09f3715329a8ddf246a

  5. 5. Combine step 3

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

    printf '01%s%s' "7b7afb342e521901bc3203dcfc02476d8a86c344d98b10ea9135817edcc00fce" "e11551e1c82e2844519f84ed3249d1844c83f2304a7ff09f3715329a8ddf246a" | xxd -r -p | shasum -a 256

    Should print 9b61f652517d4d78b2619906032bed4a793cfb94cd760aead9f10ceb908d2f8f

  6. 6. Combine step 4

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

    printf '01%s%s' "98c37ce05d3b44441f0601a06f3b1d844fc63cbc305e7e35908bc303ceeb0659" "9b61f652517d4d78b2619906032bed4a793cfb94cd760aead9f10ceb908d2f8f" | xxd -r -p | shasum -a 256

    Should print 3a5afcf84a1bf5e336bff4d34c03792ed24edc9df5a5bbc68ade80222f91d6ed

  7. 7. Combine step 5

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

    printf '01%s%s' "3a5afcf84a1bf5e336bff4d34c03792ed24edc9df5a5bbc68ade80222f91d6ed" "68f69fa84996c11465daa44ab990c45da47c0bc64ebea34ad51180cd9223a4cf" | xxd -r -p | shasum -a 256

    Should print 625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

  8. 8. 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/0x99ce65ad3e3a0d7d4e90e274691f2ed402696c16d0feac0a1c0e5793bbe9bb06

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

Read the specification