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-0901-I5KCMJ4R
Content hash
f4b089da69fb73c0bd78040a261f3ba25ff58bd3d5ca182f1d59e0c56ee509c3
Day recorded
2026-09-01
Articles recorded that day
2
Attestation UID
0x97ee99fd17c86f4527bf0c6b02d30a0093410616d1266ed6e8b8f70d7e23afc2
View on EAS
Transaction
0xf34ef80f7b4bbf631ae6b3cd1ae44e24cefd71dc6f5fd317afc5cfc1ee629c60
View on Basescan
Stamped
1 Sept 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
0x653bea75df81ef447a7807c2ac869ce40389d2b5397a7a35ccf739bfcb959973

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
    0x42455f933c7d1ee6da7b3f0de843684d353f152b9d389fc77435b47fe803c74b
    0x56d33262fd5523ef990876f3cb3c59b6da88525c4a6080f03e28508a2495f908

    This is the value for the whole day.

Value these steps arrive at
0x56d33262fd5523ef990876f3cb3c59b6da88525c4a6080f03e28508a2495f908

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
0x56d33262fd5523ef990876f3cb3c59b6da88525c4a6080f03e28508a2495f908
Read from Base
0x56d33262fd5523ef990876f3cb3c59b6da88525c4a6080f03e28508a2495f908
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":"cardiovitahash","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"The textbook teaching is to check BP/HR lying down, then standing at 1 and 3 minutes. In practice,…

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-0901-I5KCMJ4R/canonical" | shasum -a 256

    Should print f4b089da69fb73c0bd78040a261f3ba25ff58bd3d5ca182f1d59e0c56ee509c3

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

    Should print 653bea75df81ef447a7807c2ac869ce40389d2b5397a7a35ccf739bfcb959973

  3. 3. Combine step 1

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

    printf '01%s%s' "653bea75df81ef447a7807c2ac869ce40389d2b5397a7a35ccf739bfcb959973" "42455f933c7d1ee6da7b3f0de843684d353f152b9d389fc77435b47fe803c74b" | xxd -r -p | shasum -a 256

    Should print 56d33262fd5523ef990876f3cb3c59b6da88525c4a6080f03e28508a2495f908

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

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

Read the specification