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-1024-JBJT5KNU
Content hash
60dfb8a07c1d800c50c346238bd8254e541c0c8af3b53ee1a9167e4e1234e910
Day recorded
2026-10-25
Articles recorded that day
15
Attestation UID
0xbe0cd6a2a9b10b84ae911c7f4e689595cda4703c07a00165b6843e930e66ac03
View on EAS
Transaction
0xbb4fe17ce7515554b6a9b0763c70ab8a53d9a9daa431b55c9e6c3e699f100a42
View on Basescan
Stamped
25 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
0x3a188108ec291012a9ba9b9dcee4e1864dd1f849ccae2f07fc0c588341a2b8f8

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
    0x400bf3d486ec09d1ac03fa92aac0f3b282563431aa6957e03cd035de843aa95e
    0xb4b49e40c59e86475db001a63658ef6553921f9662647b344710908e3f7f628b
  2. Step 2, combined with the value before it
    0x9cd54441cea6e55e775ec194543aa3302eca15fcab5121d797182f423c32101b
    0x5be5d2074692d8ad909f31b92ad955ec5441554cd0c6ae4e2247cbfb8b77e76d
  3. Step 3, combined with the value after it
    0x74d09ca217047e6689fba103cf04d77c2db1d86dc09a00a8c639e9203e65ea44
    0x1e9497797c1cba124fc0613737c33d5be9909c921e76f14580846d73f1b3933d
  4. Step 4, combined with the value before it
    0xff0e4f5aa35c196ec95fc9780c2f4d5b3c1425b8dbe3f7c4a3e56f7a004ad60c
    0x76e330bc108fc58c62733cc38ab8829f9b9bd8ea2dac7de66d10c45ef8cb3643

    This is the value for the whole day.

Value these steps arrive at
0x76e330bc108fc58c62733cc38ab8829f9b9bd8ea2dac7de66d10c45ef8cb3643

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
0x76e330bc108fc58c62733cc38ab8829f9b9bd8ea2dac7de66d10c45ef8cb3643
Read from Base
0x76e330bc108fc58c62733cc38ab8829f9b9bd8ea2dac7de66d10c45ef8cb3643
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,"agreement":false,"authors":[{"identity":"Drkrittanawong","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"❤️ Heart attack. No obstructive coronary disease. Now what?","type":"text"}],"ty…

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-1024-JBJT5KNU/canonical" | shasum -a 256

    Should print 60dfb8a07c1d800c50c346238bd8254e541c0c8af3b53ee1a9167e4e1234e910

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

    Should print 3a188108ec291012a9ba9b9dcee4e1864dd1f849ccae2f07fc0c588341a2b8f8

  3. 3. Combine step 1

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

    printf '01%s%s' "400bf3d486ec09d1ac03fa92aac0f3b282563431aa6957e03cd035de843aa95e" "3a188108ec291012a9ba9b9dcee4e1864dd1f849ccae2f07fc0c588341a2b8f8" | xxd -r -p | shasum -a 256

    Should print b4b49e40c59e86475db001a63658ef6553921f9662647b344710908e3f7f628b

  4. 4. Combine step 2

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

    printf '01%s%s' "9cd54441cea6e55e775ec194543aa3302eca15fcab5121d797182f423c32101b" "b4b49e40c59e86475db001a63658ef6553921f9662647b344710908e3f7f628b" | xxd -r -p | shasum -a 256

    Should print 5be5d2074692d8ad909f31b92ad955ec5441554cd0c6ae4e2247cbfb8b77e76d

  5. 5. Combine step 3

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

    printf '01%s%s' "5be5d2074692d8ad909f31b92ad955ec5441554cd0c6ae4e2247cbfb8b77e76d" "74d09ca217047e6689fba103cf04d77c2db1d86dc09a00a8c639e9203e65ea44" | xxd -r -p | shasum -a 256

    Should print 1e9497797c1cba124fc0613737c33d5be9909c921e76f14580846d73f1b3933d

  6. 6. Combine step 4

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

    printf '01%s%s' "ff0e4f5aa35c196ec95fc9780c2f4d5b3c1425b8dbe3f7c4a3e56f7a004ad60c" "1e9497797c1cba124fc0613737c33d5be9909c921e76f14580846d73f1b3933d" | xxd -r -p | shasum -a 256

    Should print 76e330bc108fc58c62733cc38ab8829f9b9bd8ea2dac7de66d10c45ef8cb3643

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

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

Read the specification