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.

📈 Stock Market Today

financeguy · 21 Aug 2026

Stamp ID
STAMP-2026-0821-M6APBIW2
Content hash
af9959e009c7758411fe1d0d310444da38753bc37ecd6888a930df20170f6ea6
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
0xc41767da1e36754ecd1f09c6543bc14a79d00c43e75778422aedf2de50950d66

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
    0x5c43500827820995c8ca2253cc354182eeba6b46f1166ac01ccdc43c4564445b
    0xd9392a2dd6385c043ffb400890bb5721ad1e51a23067d2bdf233caf4565f600d
  2. Step 2, combined with the value before it
    0xbd61b4f05584217271d493cc9bd9dc797c67218d080d14bb52b86c637fa2dacb
    0xd6410d5e51f51788bd42ba793c9866dc9b4168ad507e32e53cb04274cfde22ef
  3. Step 3, combined with the value after it
    0x0ba283e3f17a592f6b90c7c2034b2bc7a6907613565a2401a1d2c9390b376157
    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":"Wall Street rebounds, but weekly losses loom.","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-0821-M6APBIW2/canonical" | shasum -a 256

    Should print af9959e009c7758411fe1d0d310444da38753bc37ecd6888a930df20170f6ea6

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

    Should print c41767da1e36754ecd1f09c6543bc14a79d00c43e75778422aedf2de50950d66

  3. 3. Combine step 1

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

    printf '01%s%s' "5c43500827820995c8ca2253cc354182eeba6b46f1166ac01ccdc43c4564445b" "c41767da1e36754ecd1f09c6543bc14a79d00c43e75778422aedf2de50950d66" | xxd -r -p | shasum -a 256

    Should print d9392a2dd6385c043ffb400890bb5721ad1e51a23067d2bdf233caf4565f600d

  4. 4. Combine step 2

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

    printf '01%s%s' "bd61b4f05584217271d493cc9bd9dc797c67218d080d14bb52b86c637fa2dacb" "d9392a2dd6385c043ffb400890bb5721ad1e51a23067d2bdf233caf4565f600d" | xxd -r -p | shasum -a 256

    Should print d6410d5e51f51788bd42ba793c9866dc9b4168ad507e32e53cb04274cfde22ef

  5. 5. Combine step 3

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

    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