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-0829-ERVQ35DR
Content hash
3b0229c2056183e46263df6161843842c0e45a482b2214422c003189caa94d2b
Day recorded
2026-08-30
Articles recorded that day
2
Attestation UID
0x271be880893915224a8fb7d7d6b0211279fe70b4531ebb8437c1a66c9d90cd9e
View on EAS
Transaction
0x7410a3ebb0fb6ff3e7049bf9ddda7f366b2fd1e83b4fced743a7b5c620837c73
View on Basescan
Stamped
30 Aug 2026

Recorded on Base Sepolia using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other article 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
0x08506e3105dc0da61d4524bbfba31ec0dcc72b2cdeccedc13eaea1e972a395dc

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
    0x8161e40f02e21749b2baf0042bd93b4fa8b8327dc442b8dea8a464d783ff82b4
    0xf884a18700ed8abea549570ed7f0ed9f6a2e75f48885ce6716473b90bca159cc

    This is the value for the whole day.

Value these steps arrive at
0xf884a18700ed8abea549570ed7f0ed9f6a2e75f48885ce6716473b90bca159cc

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
0xf884a18700ed8abea549570ed7f0ed9f6a2e75f48885ce6716473b90bca159cc
Read from Base
0xf884a18700ed8abea549570ed7f0ed9f6a2e75f48885ce6716473b90bca159cc
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,"authors":[{"identity":"krittanawongmd","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"The new ACC/AHA Clinical Performance and Quality Measures for Peripheral Artery Disease (PAD) are …

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-0829-ERVQ35DR/canonical" | shasum -a 256

    Should print 3b0229c2056183e46263df6161843842c0e45a482b2214422c003189caa94d2b

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

    Should print 08506e3105dc0da61d4524bbfba31ec0dcc72b2cdeccedc13eaea1e972a395dc

  3. 3. Combine step 1

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

    printf '01%s%s' "8161e40f02e21749b2baf0042bd93b4fa8b8327dc442b8dea8a464d783ff82b4" "08506e3105dc0da61d4524bbfba31ec0dcc72b2cdeccedc13eaea1e972a395dc" | xxd -r -p | shasum -a 256

    Should print f884a18700ed8abea549570ed7f0ed9f6a2e75f48885ce6716473b90bca159cc

  4. 4. 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-sepolia.easscan.org/attestation/view/0x271be880893915224a8fb7d7d6b0211279fe70b4531ebb8437c1a66c9d90cd9e

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

Read the specification