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.

The Obesity-Heart Disease Connection: Is Weight Loss the New Cardiovascular Prevention?

Sarib Sultan, Scott Isaacs, MD, FACP, FACE, Chayakrit Krittanawong, MD, FACC, FAHA, FSCAI · 30 Oct 2026

Stamp ID
STAMP-2026-1030-LJ4T6GBK
Content hash
0ccd70d1f2b598eab89e8f61a3d8fbc9356ed8f65ba57d076e27276fd4509be6
Day recorded
2026-10-30
Articles recorded that day
15
Attestation UID
0x8a0c10ce03592e13c4ce122e3babd8fcc9ffed2a274e6bad4a519029f53173c8
View on EAS
Transaction
0xe649e16f8f76c6fb5515456bd972c25015f49a6f03c541c81135262804602ab5
View on Basescan
Stamped
30 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
0xb3149632108d722b9f55cb008e0aeefdf11bc5665b1c9406f3158997fd1bf8d4

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
    0xbd318f0dde84ad293cce71bed9c5b000e29b02c6e63f754d7ff14dc87ab0b0e6
    0x9cc18f589797f54990db94e897012704840b154c6a0ea0c80738b86afaaf3739
  2. Step 2, combined with the value after it
    0x8699b2066a1fca44528204506e558dfbc37433a5ff91d038d4a6f05b709fca31
    0x2dc3a1231dfbc1630de8e551c012aaf03584e0553a81a9f8574879e6cffea082
  3. Step 3, combined with the value before it
    0x6e720b3f0408bba781fba2a8b0b402de47add4de9b4bc4f56efaa51370c2b89c
    0xc25eb6e9187995c8dc97a8ed32371aa6eca00d9612aa823971dd23febed2f330
  4. Step 4, combined with the value before it
    0xa25067886337ab5683d494cb956e6fe08115f907cc4e1f59a5cae62147d46624
    0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

    This is the value for the whole day.

Value these steps arrive at
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

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
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84
Read from Base
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84
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":"Obesity affects more than one billion people worldwide and is a major upstream driver of cardiovascular disease (CVD). Dysfunctional visceral adipose tissue acts as an active endocrine organ, promoting insulin resistance, lipot…

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-1030-LJ4T6GBK/canonical" | shasum -a 256

    Should print 0ccd70d1f2b598eab89e8f61a3d8fbc9356ed8f65ba57d076e27276fd4509be6

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

    Should print b3149632108d722b9f55cb008e0aeefdf11bc5665b1c9406f3158997fd1bf8d4

  3. 3. Combine step 1

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

    printf '01%s%s' "b3149632108d722b9f55cb008e0aeefdf11bc5665b1c9406f3158997fd1bf8d4" "bd318f0dde84ad293cce71bed9c5b000e29b02c6e63f754d7ff14dc87ab0b0e6" | xxd -r -p | shasum -a 256

    Should print 9cc18f589797f54990db94e897012704840b154c6a0ea0c80738b86afaaf3739

  4. 4. Combine step 2

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

    printf '01%s%s' "9cc18f589797f54990db94e897012704840b154c6a0ea0c80738b86afaaf3739" "8699b2066a1fca44528204506e558dfbc37433a5ff91d038d4a6f05b709fca31" | xxd -r -p | shasum -a 256

    Should print 2dc3a1231dfbc1630de8e551c012aaf03584e0553a81a9f8574879e6cffea082

  5. 5. Combine step 3

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

    printf '01%s%s' "6e720b3f0408bba781fba2a8b0b402de47add4de9b4bc4f56efaa51370c2b89c" "2dc3a1231dfbc1630de8e551c012aaf03584e0553a81a9f8574879e6cffea082" | xxd -r -p | shasum -a 256

    Should print c25eb6e9187995c8dc97a8ed32371aa6eca00d9612aa823971dd23febed2f330

  6. 6. Combine step 4

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

    printf '01%s%s' "a25067886337ab5683d494cb956e6fe08115f907cc4e1f59a5cae62147d46624" "c25eb6e9187995c8dc97a8ed32371aa6eca00d9612aa823971dd23febed2f330" | xxd -r -p | shasum -a 256

    Should print 4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

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

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

Read the specification