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-476QP27R
Content hash
310a6acd706c7e8a45cd688a072f8d5cf5a164f6573b0188502e1f00a6481c3b
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
0x079ae200ea70476411a7ce7ec18f9571f83906e09632ddffd7685399ccf601fe

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
    0x1f41b0260d4ed4f6bbf928e49cfeb32ffa5e3fe0dc8f4235e4fc9695cc13057e
    0x438a16cd2f91475724cb768dae1d80879013bdd8222e6ed708aeeea4ee70535c
  2. Step 2, combined with the value after it
    0x18860f543cb695a6cf1730ce8203e63e88aa59ea488aab1fc6e4fe9e7a0343a2
    0xa61b528ac31ab53ad67e464cc35c35a6703149dff4eafc4329b1effbd6200676
  3. Step 3, combined with the value after it
    0x295d3ea569536337b7ca4373b01a70ada78ded260b54759c77ac2d485a9d0d9c
    0x14f669e0f822491b9aa1b095f0db4748eb01a8b0f6ff90d70fb2427d2b51f4fd
  4. Step 4, combined with the value after it
    0x1859c02311bef9ab0164f35c8a7ce9611c0edebebcc6c8e1a0419777e31ce29a
    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":"The Maldives is an amazing vacation destination","type":"text"}],"type":"paragra…

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-476QP27R/canonical" | shasum -a 256

    Should print 310a6acd706c7e8a45cd688a072f8d5cf5a164f6573b0188502e1f00a6481c3b

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

    Should print 079ae200ea70476411a7ce7ec18f9571f83906e09632ddffd7685399ccf601fe

  3. 3. Combine step 1

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

    printf '01%s%s' "079ae200ea70476411a7ce7ec18f9571f83906e09632ddffd7685399ccf601fe" "1f41b0260d4ed4f6bbf928e49cfeb32ffa5e3fe0dc8f4235e4fc9695cc13057e" | xxd -r -p | shasum -a 256

    Should print 438a16cd2f91475724cb768dae1d80879013bdd8222e6ed708aeeea4ee70535c

  4. 4. Combine step 2

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

    printf '01%s%s' "438a16cd2f91475724cb768dae1d80879013bdd8222e6ed708aeeea4ee70535c" "18860f543cb695a6cf1730ce8203e63e88aa59ea488aab1fc6e4fe9e7a0343a2" | xxd -r -p | shasum -a 256

    Should print a61b528ac31ab53ad67e464cc35c35a6703149dff4eafc4329b1effbd6200676

  5. 5. Combine step 3

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

    printf '01%s%s' "a61b528ac31ab53ad67e464cc35c35a6703149dff4eafc4329b1effbd6200676" "295d3ea569536337b7ca4373b01a70ada78ded260b54759c77ac2d485a9d0d9c" | xxd -r -p | shasum -a 256

    Should print 14f669e0f822491b9aa1b095f0db4748eb01a8b0f6ff90d70fb2427d2b51f4fd

  6. 6. Combine step 4

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

    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