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.

Buying the panic

financeguy · 15 Aug 2026

Stamp ID
STAMP-2026-0815-5VOSEZMD
Content hash
b7df6ee7195603885de8f306bfb6b44e1bca1b68e4e31b60ea3f6eda3fc05441
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
0x302454cf741cb75299adbb30bd5e1fd90b746c9004dd61055a31e7331b47cf97

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
    0xb24dd1721465384c8b01206e75573de28261f8db943f82dff8e46b781a5654b7
    0xd366255d955fa1bee213b05e728197df6296ced6e66463d9a2dbf36f33f765a9
  2. Step 2, combined with the value after it
    0x2c0c43b11d06d0745d28f7952256bc5b3a91aa90b4c91cc507229aac6dd5ee0d
    0x593538db96a77df83adfe01eaad0ae7618f6047e2f423e3e56abae608f61dcc7
  3. Step 3, combined with the value before it
    0x6c9e8ea96a46de35ddfa812017450b5aacecf3472331e8faf90eee89419c3c36
    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":"People got rich in 2008 buying the panic. ","type":"text"}],"type":"paragraph"},{"content":[{"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-0815-5VOSEZMD/canonical" | shasum -a 256

    Should print b7df6ee7195603885de8f306bfb6b44e1bca1b68e4e31b60ea3f6eda3fc05441

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

    Should print 302454cf741cb75299adbb30bd5e1fd90b746c9004dd61055a31e7331b47cf97

  3. 3. Combine step 1

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

    printf '01%s%s' "302454cf741cb75299adbb30bd5e1fd90b746c9004dd61055a31e7331b47cf97" "b24dd1721465384c8b01206e75573de28261f8db943f82dff8e46b781a5654b7" | xxd -r -p | shasum -a 256

    Should print d366255d955fa1bee213b05e728197df6296ced6e66463d9a2dbf36f33f765a9

  4. 4. Combine step 2

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

    printf '01%s%s' "d366255d955fa1bee213b05e728197df6296ced6e66463d9a2dbf36f33f765a9" "2c0c43b11d06d0745d28f7952256bc5b3a91aa90b4c91cc507229aac6dd5ee0d" | xxd -r -p | shasum -a 256

    Should print 593538db96a77df83adfe01eaad0ae7618f6047e2f423e3e56abae608f61dcc7

  5. 5. Combine step 3

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

    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