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.

You can only pick ONE to bring back for the weekend.

financeguy · 20 Sept 2026

Stamp ID
STAMP-2026-0920-YHTMOIIW
Content hash
b46e5e58d3b1cff7a2617d4d190ed3b0f66449ddf38ff347082c7eac77115f6f
Day recorded
2026-09-21
Articles recorded that day
19
Attestation UID
0x8b3c2fd36a922edc6b9b5df7a32564ad6b8254e5e4d73310406d45385ea13aef
View on EAS
Transaction
0x7487c62e52e4f2f9b08c668465c50f1ad9bf79791f45570457388f46bcdbb8aa
View on Basescan
Stamped
22 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0x45ab660afd9ff7aff7a686ab675afa3e540fe2375c3c3824ecedd6cb2ec9c8eb

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
    0xd9b2c71fc2050b9649281191e44bbdbfcf08b9a72aee24716b1c1bb2d73b4194
    0x5a00a6470eb0e03221a6cf299ca2269d5768117115b12adf1803d69eac9a8bf0
  2. Step 2, combined with the value after it
    0xd91ff408d551afec7b21779779b3829604898af4067192fc508a792ab1e1c3d1
    0x9ea770e708ff5a992ebbe1dc432ce6a573002e55cb9a4793a315029f9ce7b7ec
  3. Step 3, combined with the value before it
    0x2e6ebaca17a3bf1331e377895837d2a1ed000ada39219e6311b1166e1f7b9603
    0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31

    This is the value for the whole day.

Value these steps arrive at
0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31

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
0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31
Read from Base
0x86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31
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":"I just touched grass today and honestly felt so much better. 🌱 Sometimes a little fr…

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-0920-YHTMOIIW/canonical" | shasum -a 256

    Should print b46e5e58d3b1cff7a2617d4d190ed3b0f66449ddf38ff347082c7eac77115f6f

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

    Should print 45ab660afd9ff7aff7a686ab675afa3e540fe2375c3c3824ecedd6cb2ec9c8eb

  3. 3. Combine step 1

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

    printf '01%s%s' "d9b2c71fc2050b9649281191e44bbdbfcf08b9a72aee24716b1c1bb2d73b4194" "45ab660afd9ff7aff7a686ab675afa3e540fe2375c3c3824ecedd6cb2ec9c8eb" | xxd -r -p | shasum -a 256

    Should print 5a00a6470eb0e03221a6cf299ca2269d5768117115b12adf1803d69eac9a8bf0

  4. 4. Combine step 2

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

    printf '01%s%s' "5a00a6470eb0e03221a6cf299ca2269d5768117115b12adf1803d69eac9a8bf0" "d91ff408d551afec7b21779779b3829604898af4067192fc508a792ab1e1c3d1" | xxd -r -p | shasum -a 256

    Should print 9ea770e708ff5a992ebbe1dc432ce6a573002e55cb9a4793a315029f9ce7b7ec

  5. 5. Combine step 3

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

    printf '01%s%s' "2e6ebaca17a3bf1331e377895837d2a1ed000ada39219e6311b1166e1f7b9603" "9ea770e708ff5a992ebbe1dc432ce6a573002e55cb9a4793a315029f9ce7b7ec" | xxd -r -p | shasum -a 256

    Should print 86fe5b1cd501a45cbc53b8151487586f6954bc5f77a2874f0eb0602698444b31

  6. 6. 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/0x8b3c2fd36a922edc6b9b5df7a32564ad6b8254e5e4d73310406d45385ea13aef

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

Read the specification