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-1112-FNONBMCF
Content hash
157b4dc5fd4a55b0a829d68bc6410fc213312377cd0419f47ed00413fb97f528
Day recorded
2026-11-13
Articles recorded that day
13
Attestation UID
0x8d2d037d35d1d2f5ebd7ff95f0014255d2bcbac020bb3776b5cf710ca2ef0261
View on EAS
Transaction
0x39f12d8f2e595c717b4bce40bb59a5b28ba569bd14374bedff8237b5b15fd65f
View on Basescan
Stamped
13 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 12 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
0x9bfba885eb51000762a9fa2b54a8e8aacd5deba9e6b2e03eec8d9eef8286f292

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
    0x57ac41798ebb12d9cfa62bc912dc8d6c1fb4c38b4ab216b84ed96ddd5560c70a
    0x83197e0db13fe38f8f90bd72d4616122eda65a53c19dfc0d703ab5790d4b8389
  2. Step 2, combined with the value after it
    0x28c50f3cb686e95455c18e308bb551f18702504d68a2edf447a4c7086ff36a53
    0x8579a1fcc329bd96d865b1c1bb98e9e63f191eadf35db210047e545c2804f5a6
  3. Step 3, combined with the value after it
    0x9a4f9b9a0dedc86dee7f155e2d187caf30bf6587ddee5121c729b4cd7a10050d
    0xc686ce1ad37287ba022494162d00d61e0f5cbbe1a6acba7f779824cf91156f85
  4. Step 4, combined with the value after it
    0xff35541912e2df2feec01871825d1d7f08f12c52f251394d82803cd3c7ed73aa
    0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

    This is the value for the whole day.

Value these steps arrive at
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

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
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d
Read from Base
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d
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":"financeguy","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Imagine you buy a house for $400,000.","type":"text"}],"type":"paragraph"},{"content…

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-1112-FNONBMCF/canonical" | shasum -a 256

    Should print 157b4dc5fd4a55b0a829d68bc6410fc213312377cd0419f47ed00413fb97f528

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

    Should print 9bfba885eb51000762a9fa2b54a8e8aacd5deba9e6b2e03eec8d9eef8286f292

  3. 3. Combine step 1

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

    printf '01%s%s' "57ac41798ebb12d9cfa62bc912dc8d6c1fb4c38b4ab216b84ed96ddd5560c70a" "9bfba885eb51000762a9fa2b54a8e8aacd5deba9e6b2e03eec8d9eef8286f292" | xxd -r -p | shasum -a 256

    Should print 83197e0db13fe38f8f90bd72d4616122eda65a53c19dfc0d703ab5790d4b8389

  4. 4. Combine step 2

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

    printf '01%s%s' "83197e0db13fe38f8f90bd72d4616122eda65a53c19dfc0d703ab5790d4b8389" "28c50f3cb686e95455c18e308bb551f18702504d68a2edf447a4c7086ff36a53" | xxd -r -p | shasum -a 256

    Should print 8579a1fcc329bd96d865b1c1bb98e9e63f191eadf35db210047e545c2804f5a6

  5. 5. Combine step 3

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

    printf '01%s%s' "8579a1fcc329bd96d865b1c1bb98e9e63f191eadf35db210047e545c2804f5a6" "9a4f9b9a0dedc86dee7f155e2d187caf30bf6587ddee5121c729b4cd7a10050d" | xxd -r -p | shasum -a 256

    Should print c686ce1ad37287ba022494162d00d61e0f5cbbe1a6acba7f779824cf91156f85

  6. 6. Combine step 4

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

    printf '01%s%s' "c686ce1ad37287ba022494162d00d61e0f5cbbe1a6acba7f779824cf91156f85" "ff35541912e2df2feec01871825d1d7f08f12c52f251394d82803cd3c7ed73aa" | xxd -r -p | shasum -a 256

    Should print 173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

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

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

Read the specification