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-1021-KX6MNJSP
Content hash
2c2dbfaeb26470302d6dd07af3fa391d466a357c28b8989922217a4c5c97cfa6
Day recorded
2026-10-21
Articles recorded that day
16
Attestation UID
0x89ef6a9a41317f2387365d0b0696b17f5e37afee4180e22971cbbdab39001cbd
View on EAS
Transaction
0x6418cae6be9428e44ef11ff61beaab45ad0660d9fd102dcd81c3e1cc3447db0c
View on Basescan
Stamped
21 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 15 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
0x9b48bdc0b10703b500d6aa4c6bbb2721d19a988eaf65393c725d51284c67ffa7

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
    0xba13b4e6bbf13f11bccad2c322086ce3266a7fbab216b1ee0a9c7e8f049f38a6
    0x329c427872b73cb928a7a245a02e943a296c362280d5d80d05cb0b2ba4ec0369
  2. Step 2, combined with the value before it
    0x98d1344bc2f1a75b493f633e891f8cc106a722edc253efe0b015aa9628b63f92
    0x314d0d1e4452c1976718b8fe8559153b9a6fc9982b75eb3bbd7520f2aecf3db4
  3. Step 3, combined with the value before it
    0x2b08533c4494657626ccff5afa9bfbf5599edbf859ddcc53a4c7265025e02e05
    0xb2f73bf44e5192607c06210438c4fa1315c46c1daf818f9ef4da8afd94550031
  4. Step 4, combined with the value before it
    0x3a358e17a68391bcf565bd61d36701a1116f99db25af510c143423c88a16c1e8
    0x109188c0f9ad19ad1583a0ded4c3846a0c340392774326fc93cb283681e809ec

    This is the value for the whole day.

Value these steps arrive at
0x109188c0f9ad19ad1583a0ded4c3846a0c340392774326fc93cb283681e809ec

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
0x109188c0f9ad19ad1583a0ded4c3846a0c340392774326fc93cb283681e809ec
Read from Base
0x109188c0f9ad19ad1583a0ded4c3846a0c340392774326fc93cb283681e809ec
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":"The working diagnosis of Myocardial Infarction with Non-Obstructive Coronary Arteries (MINOCA) is a heterogeneous clinical entity that includes true ischemic etiologies and MINOCA mimickers, and accounts for approximately 4-15%…

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-1021-KX6MNJSP/canonical" | shasum -a 256

    Should print 2c2dbfaeb26470302d6dd07af3fa391d466a357c28b8989922217a4c5c97cfa6

  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-1021-KX6MNJSP CONTENT=2c2dbfaeb26470302d6dd07af3fa391d466a357c28b8989922217a4c5c97cfa6 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 9b48bdc0b10703b500d6aa4c6bbb2721d19a988eaf65393c725d51284c67ffa7

  3. 3. Combine step 1

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

    printf '01%s%s' "ba13b4e6bbf13f11bccad2c322086ce3266a7fbab216b1ee0a9c7e8f049f38a6" "9b48bdc0b10703b500d6aa4c6bbb2721d19a988eaf65393c725d51284c67ffa7" | xxd -r -p | shasum -a 256

    Should print 329c427872b73cb928a7a245a02e943a296c362280d5d80d05cb0b2ba4ec0369

  4. 4. Combine step 2

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

    printf '01%s%s' "98d1344bc2f1a75b493f633e891f8cc106a722edc253efe0b015aa9628b63f92" "329c427872b73cb928a7a245a02e943a296c362280d5d80d05cb0b2ba4ec0369" | xxd -r -p | shasum -a 256

    Should print 314d0d1e4452c1976718b8fe8559153b9a6fc9982b75eb3bbd7520f2aecf3db4

  5. 5. Combine step 3

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

    printf '01%s%s' "2b08533c4494657626ccff5afa9bfbf5599edbf859ddcc53a4c7265025e02e05" "314d0d1e4452c1976718b8fe8559153b9a6fc9982b75eb3bbd7520f2aecf3db4" | xxd -r -p | shasum -a 256

    Should print b2f73bf44e5192607c06210438c4fa1315c46c1daf818f9ef4da8afd94550031

  6. 6. Combine step 4

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

    printf '01%s%s' "3a358e17a68391bcf565bd61d36701a1116f99db25af510c143423c88a16c1e8" "b2f73bf44e5192607c06210438c4fa1315c46c1daf818f9ef4da8afd94550031" | xxd -r -p | shasum -a 256

    Should print 109188c0f9ad19ad1583a0ded4c3846a0c340392774326fc93cb283681e809ec

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

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

Read the specification