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.

Stamp ID
STAMP-2026-1016-PYHB5RJO
Content hash
4cb1a4d4fc12e87cfeb563858e6ba6f83ca9b5affd98cb7c61dadad57f730928
Day recorded
2026-10-16
Articles recorded that day
15
Attestation UID
0x3df2f9bba5f8c8f68525dd8899d238bcdb9b22e0d77e200602c1a7297409ec08
View on EAS
Transaction
0xc39ca09b13e94230f38c7d78f8a6fce218c3cdcd556d187e9ad2eca15e97844a
View on Basescan
Stamped
16 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
0xfb8913efa84c090404afdb0009fa2eddc80620d989da18c78d8873acbd0377e7

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
    0xf9dbb15e1ea4a63d789d7500778a12b2073cf91d08858b9b163f7f8ac883e4a4
    0xfb077f8818a6419898d5c44167d42ddde5b3f21c344eaba9b1b8ceb16493d586
  2. Step 2, combined with the value before it
    0xae4bf605f864161b4ae0a66aca9f816369367939400cf4ef7c301d588968fde5
    0x3f35dda989b44713b461e12fde10135e74de137c15ca7c28c15994b6b123b110
  3. Step 3, combined with the value before it
    0xa5e2a46c5ef458f7ab84cafd04570be68d5d89c631f3d01eaf64fc4dfd254949
    0xccf3b111c5b1899fc8e85a798afb5bf869aaa8ef2f757dc87e0691e472931bd2

    This is the value for the whole day.

Value these steps arrive at
0xccf3b111c5b1899fc8e85a798afb5bf869aaa8ef2f757dc87e0691e472931bd2

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
0xccf3b111c5b1899fc8e85a798afb5bf869aaa8ef2f757dc87e0691e472931bd2
Read from Base
0xccf3b111c5b1899fc8e85a798afb5bf869aaa8ef2f757dc87e0691e472931bd2
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\nTranscatheter tricuspid valve interventions (TTVI) have transformed the management of severe tricuspid regurgitation (TR). Although randomized trials have consistently shown improvements in TR severity, symptoms, an…

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-1016-PYHB5RJO/canonical" | shasum -a 256

    Should print 4cb1a4d4fc12e87cfeb563858e6ba6f83ca9b5affd98cb7c61dadad57f730928

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

    Should print fb8913efa84c090404afdb0009fa2eddc80620d989da18c78d8873acbd0377e7

  3. 3. Combine step 1

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

    printf '01%s%s' "f9dbb15e1ea4a63d789d7500778a12b2073cf91d08858b9b163f7f8ac883e4a4" "fb8913efa84c090404afdb0009fa2eddc80620d989da18c78d8873acbd0377e7" | xxd -r -p | shasum -a 256

    Should print fb077f8818a6419898d5c44167d42ddde5b3f21c344eaba9b1b8ceb16493d586

  4. 4. Combine step 2

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

    printf '01%s%s' "ae4bf605f864161b4ae0a66aca9f816369367939400cf4ef7c301d588968fde5" "fb077f8818a6419898d5c44167d42ddde5b3f21c344eaba9b1b8ceb16493d586" | xxd -r -p | shasum -a 256

    Should print 3f35dda989b44713b461e12fde10135e74de137c15ca7c28c15994b6b123b110

  5. 5. Combine step 3

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

    printf '01%s%s' "a5e2a46c5ef458f7ab84cafd04570be68d5d89c631f3d01eaf64fc4dfd254949" "3f35dda989b44713b461e12fde10135e74de137c15ca7c28c15994b6b123b110" | xxd -r -p | shasum -a 256

    Should print ccf3b111c5b1899fc8e85a798afb5bf869aaa8ef2f757dc87e0691e472931bd2

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

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

Read the specification