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.

🚨 Why BTC is ripping higher

financeguy · 21 Aug 2026

Stamp ID
STAMP-2026-0821-MLI6QVWV
Content hash
fa82eaeca58399bfe557bb87eafd86e69ca499ce41ce82c308333e95055189b8
Day recorded
2026-08-22
Articles recorded that day
8
Attestation UID
0x8b842d199571d6c0fc24d9c116281a88910e1e0caaedecb8db56de60e25e90a9
View on EAS
Transaction
0xd4dd0e1dcd20b11f53267636a0a34bd581187ed621ab2812358b0571f092731c
View on Basescan
Stamped
22 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 7 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
0x87292d92cc2f83c59c7c4d50f4a7c86d233a684bf9f178869acd7e15259595c4

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
    0xd7740567381735336de7ef8e8024293ca65825b7d7ec8a6dfce0fb0f65e2e2f2
    0x306aefb4b1e85999b895fbed12702569baddc2d243d0517a3ec3643bc37b3707
  2. Step 2, combined with the value after it
    0xe2b88e380829b1c0e199b35157c5473d1bdeb8707721c426367b03afce75a774
    0x0ba283e3f17a592f6b90c7c2034b2bc7a6907613565a2401a1d2c9390b376157
  3. Step 3, combined with the value before it
    0xd6410d5e51f51788bd42ba793c9866dc9b4168ad507e32e53cb04274cfde22ef
    0xc24aec2745b7de4fa00ca459520e6e767a593720e8654115153e290b2967b1e5

    This is the value for the whole day.

Value these steps arrive at
0xc24aec2745b7de4fa00ca459520e6e767a593720e8654115153e290b2967b1e5

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
0xc24aec2745b7de4fa00ca459520e6e767a593720e8654115153e290b2967b1e5
Read from Base
0xc24aec2745b7de4fa00ca459520e6e767a593720e8654115153e290b2967b1e5
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":"Treasury Sec. Bessent says long-dated Treasury buybacks could exceed $4B per operation.","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-0821-MLI6QVWV/canonical" | shasum -a 256

    Should print fa82eaeca58399bfe557bb87eafd86e69ca499ce41ce82c308333e95055189b8

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

    Should print 87292d92cc2f83c59c7c4d50f4a7c86d233a684bf9f178869acd7e15259595c4

  3. 3. Combine step 1

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

    printf '01%s%s' "87292d92cc2f83c59c7c4d50f4a7c86d233a684bf9f178869acd7e15259595c4" "d7740567381735336de7ef8e8024293ca65825b7d7ec8a6dfce0fb0f65e2e2f2" | xxd -r -p | shasum -a 256

    Should print 306aefb4b1e85999b895fbed12702569baddc2d243d0517a3ec3643bc37b3707

  4. 4. Combine step 2

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

    printf '01%s%s' "306aefb4b1e85999b895fbed12702569baddc2d243d0517a3ec3643bc37b3707" "e2b88e380829b1c0e199b35157c5473d1bdeb8707721c426367b03afce75a774" | xxd -r -p | shasum -a 256

    Should print 0ba283e3f17a592f6b90c7c2034b2bc7a6907613565a2401a1d2c9390b376157

  5. 5. Combine step 3

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

    printf '01%s%s' "d6410d5e51f51788bd42ba793c9866dc9b4168ad507e32e53cb04274cfde22ef" "0ba283e3f17a592f6b90c7c2034b2bc7a6907613565a2401a1d2c9390b376157" | xxd -r -p | shasum -a 256

    Should print c24aec2745b7de4fa00ca459520e6e767a593720e8654115153e290b2967b1e5

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

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

Read the specification