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.

BTC

financeguy · 19 Sept 2026

Stamp ID
STAMP-2026-0919-KNNGDBYL
Content hash
0b0d06a47506892091dbee49a2e232ed1e745cb1d71f5adda50b3e590ea9211d
Day recorded
2026-09-20
Articles recorded that day
18
Attestation UID
0x1ed0b640723183fed258fb97c6562ff95da0496d1406e14653e12c062865f9d3
View on EAS
Transaction
0x7b9fdc49a1760db010f3985639be208da0d433b5b3f9fa84e64abdaa135d36d6
View on Basescan
Stamped
21 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 17 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
0x0ed67405f856db336dd6151bceffc30f71845f960f67e57b7dcfbe3dec4de3d0

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
    0x733ba2b0d1c059b209c5c5cc3f93362e43f46ab9386cae245ba0e6dbf44e532c
    0x43a125bfd3f57248313d7555f5b90b3225ee73a469f18823e9c6690e2be5cbd2
  2. Step 2, combined with the value after it
    0xe13bf695535a1e67d382f9707e478589ed555e9196c942269c09932dd9d0e2a9
    0x4c4970dd96aad6ebb5840b1c36e099ec5e477a60e21b738c1f75ecf72dd79fdb
  3. Step 3, combined with the value after it
    0xdfe86050bde6474cfac0f473484524caab9066cb2c189566cfe3a79de76390b1
    0x88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3
  4. Step 4, combined with the value before it
    0x6ddc36faf65fa6578b988653de332a1f027710b88843c4a0b1ff15f7b542a8ed
    0x55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567
  5. Step 5, combined with the value after it
    0x2544de35a4de67f9861a894e1a2eed77c03547acb509e6b8af67a233143738ac
    0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997

    This is the value for the whole day.

Value these steps arrive at
0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997

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
0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997
Read from Base
0x604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997
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":"If you’re in crypto, the next 6 months could be very interesting. 👀","type":"text"}]…

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-0919-KNNGDBYL/canonical" | shasum -a 256

    Should print 0b0d06a47506892091dbee49a2e232ed1e745cb1d71f5adda50b3e590ea9211d

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

    Should print 0ed67405f856db336dd6151bceffc30f71845f960f67e57b7dcfbe3dec4de3d0

  3. 3. Combine step 1

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

    printf '01%s%s' "0ed67405f856db336dd6151bceffc30f71845f960f67e57b7dcfbe3dec4de3d0" "733ba2b0d1c059b209c5c5cc3f93362e43f46ab9386cae245ba0e6dbf44e532c" | xxd -r -p | shasum -a 256

    Should print 43a125bfd3f57248313d7555f5b90b3225ee73a469f18823e9c6690e2be5cbd2

  4. 4. Combine step 2

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

    printf '01%s%s' "43a125bfd3f57248313d7555f5b90b3225ee73a469f18823e9c6690e2be5cbd2" "e13bf695535a1e67d382f9707e478589ed555e9196c942269c09932dd9d0e2a9" | xxd -r -p | shasum -a 256

    Should print 4c4970dd96aad6ebb5840b1c36e099ec5e477a60e21b738c1f75ecf72dd79fdb

  5. 5. Combine step 3

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

    printf '01%s%s' "4c4970dd96aad6ebb5840b1c36e099ec5e477a60e21b738c1f75ecf72dd79fdb" "dfe86050bde6474cfac0f473484524caab9066cb2c189566cfe3a79de76390b1" | xxd -r -p | shasum -a 256

    Should print 88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3

  6. 6. Combine step 4

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

    printf '01%s%s' "6ddc36faf65fa6578b988653de332a1f027710b88843c4a0b1ff15f7b542a8ed" "88ae246968a8ec7aa1f6b0bda6d083ecc19de338136c0c6a5e32a081fd1fe6b3" | xxd -r -p | shasum -a 256

    Should print 55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567

  7. 7. Combine step 5

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

    printf '01%s%s' "55efe9c5ee1a98cc9194ca6df5c4bf2a9a53b4e50d9ad3ea34bf27437915d567" "2544de35a4de67f9861a894e1a2eed77c03547acb509e6b8af67a233143738ac" | xxd -r -p | shasum -a 256

    Should print 604c8251ec88e064e22355a066f4db7fea15afe24d6ee73fac3f907cdf446997

  8. 8. 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/0x1ed0b640723183fed258fb97c6562ff95da0496d1406e14653e12c062865f9d3

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

Read the specification