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-1114-ORFZSGEE
Content hash
47e709ad033f4b2a7bf2e40e5646ac6d597061e68a0e73f845671e40e03cf014
Day recorded
2026-11-15
Articles recorded that day
14
Attestation UID
0x31e463c2c014894a950e60332dc4a850f4482d4bf541d8445a6417fc13588be3
View on EAS
Transaction
0xdfac994ad9e349175372ed34a4eb76def9d8213d9dd72c1f06b05dced470dc92
View on Basescan
Stamped
15 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0xeae2608422f48e1d4626aadd3a1259ecb446d635e69c47ccf4044df3aeaa2464

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
    0xff6d6ce4c8e774f18c5eb8f8b177de515642b8c391153b0fdc165afe735f7100
    0x290c3147453deefde009d0cd78fbcde5657a855c2ed6a4e154fc2e00acd0296d
  2. Step 2, combined with the value before it
    0x60768e591de78c07e726b5884dd9a45094a6f7339613558b9026bcde5e5e41ed
    0x84cc3a8a3bb0d9dd794b603b530614e86510448f83dc11f8813adacfb0663d5a
  3. Step 3, combined with the value after it
    0xc7369fb5094394b3b89c0478f5ca97c4f2ca2cbc8575a402a2e4cbf4cf461d24
    0x1859c02311bef9ab0164f35c8a7ce9611c0edebebcc6c8e1a0419777e31ce29a
  4. Step 4, combined with the value before it
    0x14f669e0f822491b9aa1b095f0db4748eb01a8b0f6ff90d70fb2427d2b51f4fd
    0x5a3523486bafdd9b9e99aeab89f000cb1329233baf4bb260ac478bf2d1dd7aae

    This is the value for the whole day.

Value these steps arrive at
0x5a3523486bafdd9b9e99aeab89f000cb1329233baf4bb260ac478bf2d1dd7aae

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
0x5a3523486bafdd9b9e99aeab89f000cb1329233baf4bb260ac478bf2d1dd7aae
Read from Base
0x5a3523486bafdd9b9e99aeab89f000cb1329233baf4bb260ac478bf2d1dd7aae
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":"🚨 Visceral fat doesn’t just expand your waistline. It damages your heart.","type…

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-1114-ORFZSGEE/canonical" | shasum -a 256

    Should print 47e709ad033f4b2a7bf2e40e5646ac6d597061e68a0e73f845671e40e03cf014

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

    Should print eae2608422f48e1d4626aadd3a1259ecb446d635e69c47ccf4044df3aeaa2464

  3. 3. Combine step 1

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

    printf '01%s%s' "eae2608422f48e1d4626aadd3a1259ecb446d635e69c47ccf4044df3aeaa2464" "ff6d6ce4c8e774f18c5eb8f8b177de515642b8c391153b0fdc165afe735f7100" | xxd -r -p | shasum -a 256

    Should print 290c3147453deefde009d0cd78fbcde5657a855c2ed6a4e154fc2e00acd0296d

  4. 4. Combine step 2

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

    printf '01%s%s' "60768e591de78c07e726b5884dd9a45094a6f7339613558b9026bcde5e5e41ed" "290c3147453deefde009d0cd78fbcde5657a855c2ed6a4e154fc2e00acd0296d" | xxd -r -p | shasum -a 256

    Should print 84cc3a8a3bb0d9dd794b603b530614e86510448f83dc11f8813adacfb0663d5a

  5. 5. Combine step 3

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

    printf '01%s%s' "84cc3a8a3bb0d9dd794b603b530614e86510448f83dc11f8813adacfb0663d5a" "c7369fb5094394b3b89c0478f5ca97c4f2ca2cbc8575a402a2e4cbf4cf461d24" | xxd -r -p | shasum -a 256

    Should print 1859c02311bef9ab0164f35c8a7ce9611c0edebebcc6c8e1a0419777e31ce29a

  6. 6. Combine step 4

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

    printf '01%s%s' "14f669e0f822491b9aa1b095f0db4748eb01a8b0f6ff90d70fb2427d2b51f4fd" "1859c02311bef9ab0164f35c8a7ce9611c0edebebcc6c8e1a0419777e31ce29a" | xxd -r -p | shasum -a 256

    Should print 5a3523486bafdd9b9e99aeab89f000cb1329233baf4bb260ac478bf2d1dd7aae

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

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

Read the specification