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.

AI bubbles or Crypto delusions

financeguy · 8 Sept 2026

Stamp ID
STAMP-2026-0908-XUFFDBN3
Content hash
a7fc42056c0171fed8b3c5d8fd860fcc3a2225fe3b8d7ec7b69ff713873ae8cf
Day recorded
2026-09-08
Articles recorded that day
5
Attestation UID
0x72fb820f58a8150de469ea4433fbf6e5bed11fe55b31d486beeb263724f9c68f
View on EAS
Transaction
0xebf9684446fbc30b804fe369ea7becf57e130f1b21b31ab6db7c5855d9f4e956
View on Basescan
Stamped
8 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 4 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
0xeee5a3c26626fad395fb57118b63a88f1e80f6b66e4305711507f83dc2625b44

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
    0xb1f432f31b9d7f2ee90004756de32083ed77dc4dd0e0c5dde26c0455101f1ebd
    0x2caabb0d80f37740a8cad7eda8118936f113d946a9a532acca7d7458790c3b08

    This is the value for the whole day.

Value these steps arrive at
0x2caabb0d80f37740a8cad7eda8118936f113d946a9a532acca7d7458790c3b08

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
0x2caabb0d80f37740a8cad7eda8118936f113d946a9a532acca7d7458790c3b08
Read from Base
0x2caabb0d80f37740a8cad7eda8118936f113d946a9a532acca7d7458790c3b08
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":"So which is the bigger illusion? AI bubbles or crypto delusions?","type":"text"}],"type":"paragraph"}]…

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-0908-XUFFDBN3/canonical" | shasum -a 256

    Should print a7fc42056c0171fed8b3c5d8fd860fcc3a2225fe3b8d7ec7b69ff713873ae8cf

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

    Should print eee5a3c26626fad395fb57118b63a88f1e80f6b66e4305711507f83dc2625b44

  3. 3. Combine step 1

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

    printf '01%s%s' "b1f432f31b9d7f2ee90004756de32083ed77dc4dd0e0c5dde26c0455101f1ebd" "eee5a3c26626fad395fb57118b63a88f1e80f6b66e4305711507f83dc2625b44" | xxd -r -p | shasum -a 256

    Should print 2caabb0d80f37740a8cad7eda8118936f113d946a9a532acca7d7458790c3b08

  4. 4. 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/0x72fb820f58a8150de469ea4433fbf6e5bed11fe55b31d486beeb263724f9c68f

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

Read the specification