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.

Financially independent myth

financeguy · 15 Aug 2026

Stamp ID
STAMP-2026-0815-2G23Q7PF
Content hash
142761c9e063443d03e8489085554598301f79abcece75ceb833cae9f3b7d01b
Day recorded
2026-08-16
Articles recorded that day
12
Attestation UID
0xbd466171c9269a1553b500cf540d4d833a73a86f8b5340dd05858ee67a202cc1
View on EAS
Transaction
0xc1f0a5866a230fc2c051c4d0a8e0f3267db91356ab65c0a169047f0e8bf72525
View on Basescan
Stamped
16 Aug 2026

Recorded on Base Sepolia using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 11 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
0x786966828aa80b3887831a5ca12fcfeef0c36b1723a7a26ae9cfe806f62b9c4b

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
    0x3de1c9c519063fb115de53cdb2dd77a98f5dd8ee8ab5e83df70c2333666c393b
    0x8978b6f409710f75fb0b46c639c8a797d1a0f126b83f1e56007238e8f0cef8b9
  2. Step 2, combined with the value after it
    0xa2905559d846a0f4ebb2eb926a23315c1891f7b64cc60d939892399c7c117467
    0x6c9e8ea96a46de35ddfa812017450b5aacecf3472331e8faf90eee89419c3c36
  3. Step 3, combined with the value after it
    0x593538db96a77df83adfe01eaad0ae7618f6047e2f423e3e56abae608f61dcc7
    0x9a459029e464b4d8a058f4a436b5f2ef4ee164eef22c325501317a042faf4e2c
  4. Step 4, combined with the value after it
    0x7ec5e373ad571f9b92df693781e92ada98745598eb8e1ffb28fac8b8743de56f
    0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

    This is the value for the whole day.

Value these steps arrive at
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

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
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef
Read from Base
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef
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,"authors":[{"identity":"financeguy","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"💸 Unpopular opinion: Financially independent people might not need a traditional emergency fund. 🤯","t…

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-0815-2G23Q7PF/canonical" | shasum -a 256

    Should print 142761c9e063443d03e8489085554598301f79abcece75ceb833cae9f3b7d01b

  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-0815-2G23Q7PF CONTENT=142761c9e063443d03e8489085554598301f79abcece75ceb833cae9f3b7d01b DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 786966828aa80b3887831a5ca12fcfeef0c36b1723a7a26ae9cfe806f62b9c4b

  3. 3. Combine step 1

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

    printf '01%s%s' "786966828aa80b3887831a5ca12fcfeef0c36b1723a7a26ae9cfe806f62b9c4b" "3de1c9c519063fb115de53cdb2dd77a98f5dd8ee8ab5e83df70c2333666c393b" | xxd -r -p | shasum -a 256

    Should print 8978b6f409710f75fb0b46c639c8a797d1a0f126b83f1e56007238e8f0cef8b9

  4. 4. Combine step 2

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

    printf '01%s%s' "8978b6f409710f75fb0b46c639c8a797d1a0f126b83f1e56007238e8f0cef8b9" "a2905559d846a0f4ebb2eb926a23315c1891f7b64cc60d939892399c7c117467" | xxd -r -p | shasum -a 256

    Should print 6c9e8ea96a46de35ddfa812017450b5aacecf3472331e8faf90eee89419c3c36

  5. 5. Combine step 3

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

    printf '01%s%s' "6c9e8ea96a46de35ddfa812017450b5aacecf3472331e8faf90eee89419c3c36" "593538db96a77df83adfe01eaad0ae7618f6047e2f423e3e56abae608f61dcc7" | xxd -r -p | shasum -a 256

    Should print 9a459029e464b4d8a058f4a436b5f2ef4ee164eef22c325501317a042faf4e2c

  6. 6. Combine step 4

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

    printf '01%s%s' "9a459029e464b4d8a058f4a436b5f2ef4ee164eef22c325501317a042faf4e2c" "7ec5e373ad571f9b92df693781e92ada98745598eb8e1ffb28fac8b8743de56f" | xxd -r -p | shasum -a 256

    Should print 7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

  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-sepolia.easscan.org/attestation/view/0xbd466171c9269a1553b500cf540d4d833a73a86f8b5340dd05858ee67a202cc1

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

Read the specification