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.

The Benefits of Optimism

@PositiveVibez · 2 Oct 2026

Stamp ID
STAMP-2026-1002-QJIR5XUT
Content hash
6510e2722aa21c412e89bc6f63ea04c1943c61759d9a50154e47cd85f337676a
Day recorded
2026-10-03
Articles recorded that day
16
Attestation UID
0xef4f7164340d74127588865a66f8ad6b4a147adaddfe66714768f453ef45889a
View on EAS
Transaction
0x323083d5c9fba3e5a84957bc6699b4170b174ca5622bd6b53ff3582408e1e794
View on Basescan
Stamped
3 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 15 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
0x90019b746a3475669c962f4f0ee738da2e2aa7060d62e020ce419d5feece291c

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
    0x6f30b0dd94224e0f8892105792e9302ae231a66fcb3c848458ea1ea956179e3a
    0xdbe13f232036c60d12c2646aa7f807b453e1777c8d0fd4875b2274394de89a56
  2. Step 2, combined with the value before it
    0x1ef4290ce8135e6e90fa8c124cef3be8fd716bac235c06c902f08f1714912b32
    0xa623326af28275fbc366a5a999fd3d7d2ac6bf6e6ce081b1cbde0bf225b72f95
  3. Step 3, combined with the value after it
    0xabf33f43100f1cad23cfecd3424bfebb9dbf02e7935a092e38f02e66963c4e2b
    0x0a8735948a3473ac9a9a57e04d8fadf11d680d37b43511e41e0f3a293772c19d
  4. Step 4, combined with the value before it
    0x17f2f01650272ea450367707dd019f7a18228797c30fcd563c069675dcd2d3ab
    0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

    This is the value for the whole day.

Value these steps arrive at
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

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
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec
Read from Base
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec
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,"agreement":false,"authors":[{"identity":"PositiveVibez","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Optimism can have a powerful effect on the way we experience everyday life. Maint…

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-1002-QJIR5XUT/canonical" | shasum -a 256

    Should print 6510e2722aa21c412e89bc6f63ea04c1943c61759d9a50154e47cd85f337676a

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

    Should print 90019b746a3475669c962f4f0ee738da2e2aa7060d62e020ce419d5feece291c

  3. 3. Combine step 1

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

    printf '01%s%s' "90019b746a3475669c962f4f0ee738da2e2aa7060d62e020ce419d5feece291c" "6f30b0dd94224e0f8892105792e9302ae231a66fcb3c848458ea1ea956179e3a" | xxd -r -p | shasum -a 256

    Should print dbe13f232036c60d12c2646aa7f807b453e1777c8d0fd4875b2274394de89a56

  4. 4. Combine step 2

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

    printf '01%s%s' "1ef4290ce8135e6e90fa8c124cef3be8fd716bac235c06c902f08f1714912b32" "dbe13f232036c60d12c2646aa7f807b453e1777c8d0fd4875b2274394de89a56" | xxd -r -p | shasum -a 256

    Should print a623326af28275fbc366a5a999fd3d7d2ac6bf6e6ce081b1cbde0bf225b72f95

  5. 5. Combine step 3

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

    printf '01%s%s' "a623326af28275fbc366a5a999fd3d7d2ac6bf6e6ce081b1cbde0bf225b72f95" "abf33f43100f1cad23cfecd3424bfebb9dbf02e7935a092e38f02e66963c4e2b" | xxd -r -p | shasum -a 256

    Should print 0a8735948a3473ac9a9a57e04d8fadf11d680d37b43511e41e0f3a293772c19d

  6. 6. Combine step 4

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

    printf '01%s%s' "17f2f01650272ea450367707dd019f7a18228797c30fcd563c069675dcd2d3ab" "0a8735948a3473ac9a9a57e04d8fadf11d680d37b43511e41e0f3a293772c19d" | xxd -r -p | shasum -a 256

    Should print ff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

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

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

Read the specification