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.

See the glass half full

@PositiveVibez · 29 Sept 2026

Stamp ID
STAMP-2026-0929-6PRWWIEE
Content hash
b6758a24e86463152ac7ec1722bb6fa2c77ffc5752e2f47726483ea3105eaa80
Day recorded
2026-09-30
Articles recorded that day
14
Attestation UID
0xa1006c6226d4a015bffa7fddabd4db5db8582a79a901a0ea1835c5a72e3fd109
View on EAS
Transaction
0xa625137b61bde7a2c0cfe8bf2d04a487d36f731ff5eb385b52213075de54c776
View on Basescan
Stamped
30 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0xa8aba1244b856ad4a9485530f1f049b91347001e414cad89db5e42fd59b3025c

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
    0x5da7a64101d480f19a3c576aca0aaadbc177c75f3138d3b3a622fb93b0e9b7fe
    0xac3aead07a173c9406e375d7b34f0dd9be2cc024154bbb47e9309f00d2722417
  2. Step 2, combined with the value after it
    0x111b4f145d2c8e912f1eb63c0525793b346b91ba9f4bffc6ac81f2464221504e
    0x64b372d3b8b7ce059ee610f05db948d18b4ad52db869c1da5e5d7eae3fc6e143
  3. Step 3, combined with the value after it
    0x792d513ef76d0c30816e13b375c164b85fba386b36c8727295bd62a32ab6fc0e
    0xe9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9
  4. Step 4, combined with the value after it
    0x9839c50d956d1a2897706be0b518a912ccfac8b30716781f1f871dc7e09c56de
    0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4

    This is the value for the whole day.

Value these steps arrive at
0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4

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
0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4
Read from Base
0x0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4
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":"Life won’t always go exactly as planned, but there’s often something good to noti…

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-0929-6PRWWIEE/canonical" | shasum -a 256

    Should print b6758a24e86463152ac7ec1722bb6fa2c77ffc5752e2f47726483ea3105eaa80

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

    Should print a8aba1244b856ad4a9485530f1f049b91347001e414cad89db5e42fd59b3025c

  3. 3. Combine step 1

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

    printf '01%s%s' "a8aba1244b856ad4a9485530f1f049b91347001e414cad89db5e42fd59b3025c" "5da7a64101d480f19a3c576aca0aaadbc177c75f3138d3b3a622fb93b0e9b7fe" | xxd -r -p | shasum -a 256

    Should print ac3aead07a173c9406e375d7b34f0dd9be2cc024154bbb47e9309f00d2722417

  4. 4. Combine step 2

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

    printf '01%s%s' "ac3aead07a173c9406e375d7b34f0dd9be2cc024154bbb47e9309f00d2722417" "111b4f145d2c8e912f1eb63c0525793b346b91ba9f4bffc6ac81f2464221504e" | xxd -r -p | shasum -a 256

    Should print 64b372d3b8b7ce059ee610f05db948d18b4ad52db869c1da5e5d7eae3fc6e143

  5. 5. Combine step 3

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

    printf '01%s%s' "64b372d3b8b7ce059ee610f05db948d18b4ad52db869c1da5e5d7eae3fc6e143" "792d513ef76d0c30816e13b375c164b85fba386b36c8727295bd62a32ab6fc0e" | xxd -r -p | shasum -a 256

    Should print e9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9

  6. 6. Combine step 4

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

    printf '01%s%s' "e9d1e5b1a20836830147c446ad7b2863ad4431cf39e511931b7447e7884c4ab9" "9839c50d956d1a2897706be0b518a912ccfac8b30716781f1f871dc7e09c56de" | xxd -r -p | shasum -a 256

    Should print 0d95ceb7226728aae5f30a457ee7fd860f8b780b977cbc834793b2d2e1fa22b4

  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/0xa1006c6226d4a015bffa7fddabd4db5db8582a79a901a0ea1835c5a72e3fd109

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

Read the specification