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.

Small changes, more positive mindset

@PositiveVibez · 24 Sept 2026

Stamp ID
STAMP-2026-0924-5FLXRZ4T
Content hash
6c4e22d6160c2fe1dae979a330d9833126c0f619b265f64a3f4ed62c5f297b7f
Day recorded
2026-09-25
Articles recorded that day
17
Attestation UID
0xb24b7d03fcf1c37c404222c77aea8f23a7442f446db95e1d2e25fb5019c66a91
View on EAS
Transaction
0xc7ded12887c12bc50ffa01bd0e2c191c565b72fca5dd7bece3f89cd683f3d759
View on Basescan
Stamped
25 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 16 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
0xd21ac8f1ea66dfc32c3ec307d0e7f59f6f925b9bbda259f5d71a5680d9ba8eb5

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
    0x02e73a9e44b86654d4474e46746d302a82a31e232749396f906b3fcdf48501f0
    0x0e07876838056510f078754761c3f40914a93e2e68b6d902bdc515a50f064a48
  2. Step 2, combined with the value before it
    0x38fd72cec5758f158a122d0559684bdaf0c04219b07b442b0446ddf067ef6314
    0x8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d
  3. Step 3, combined with the value after it
    0x33f6777026ff7882413ac506d5f631b15881c5c97af38b1bb507519f8ad7059a
    0xd47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a
  4. Step 4, combined with the value after it
    0x9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb
    0x23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b
  5. Step 5, combined with the value after it
    0x33c71efd9544bcb45a34807054911137e217cec8f6485b60035b69b93011a650
    0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4

    This is the value for the whole day.

Value these steps arrive at
0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4

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
0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4
Read from Base
0xf5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4
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":"Start your morning without immediately checking your phone.","type":"text"}],"typ…

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-0924-5FLXRZ4T/canonical" | shasum -a 256

    Should print 6c4e22d6160c2fe1dae979a330d9833126c0f619b265f64a3f4ed62c5f297b7f

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

    Should print d21ac8f1ea66dfc32c3ec307d0e7f59f6f925b9bbda259f5d71a5680d9ba8eb5

  3. 3. Combine step 1

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

    printf '01%s%s' "02e73a9e44b86654d4474e46746d302a82a31e232749396f906b3fcdf48501f0" "d21ac8f1ea66dfc32c3ec307d0e7f59f6f925b9bbda259f5d71a5680d9ba8eb5" | xxd -r -p | shasum -a 256

    Should print 0e07876838056510f078754761c3f40914a93e2e68b6d902bdc515a50f064a48

  4. 4. Combine step 2

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

    printf '01%s%s' "38fd72cec5758f158a122d0559684bdaf0c04219b07b442b0446ddf067ef6314" "0e07876838056510f078754761c3f40914a93e2e68b6d902bdc515a50f064a48" | xxd -r -p | shasum -a 256

    Should print 8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d

  5. 5. Combine step 3

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

    printf '01%s%s' "8f3520ead27ea983ec9f1c1dbb7230d7d3b5cfce0b5e0418e96cdb19e25d519d" "33f6777026ff7882413ac506d5f631b15881c5c97af38b1bb507519f8ad7059a" | xxd -r -p | shasum -a 256

    Should print d47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a

  6. 6. Combine step 4

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

    printf '01%s%s' "d47dc08efa7c65786867e25bd7b1a281946c5e4c2e0db41d294b70ed54087b1a" "9ee9c64e7435f69ae55ab7a13dc0a63ccfd6caba07976db685b158372e31f3bb" | xxd -r -p | shasum -a 256

    Should print 23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b

  7. 7. Combine step 5

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

    printf '01%s%s' "23a9bc19d01e921126f88b0bec33529da7fd454b2f693c9f4d3d6492e5dc163b" "33c71efd9544bcb45a34807054911137e217cec8f6485b60035b69b93011a650" | xxd -r -p | shasum -a 256

    Should print f5b3180edd7537457bb2566f3d46b0baf49cdd68b6c62bc4072e97c75d9b35d4

  8. 8. 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/0xb24b7d03fcf1c37c404222c77aea8f23a7442f446db95e1d2e25fb5019c66a91

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

Read the specification