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.

Choose a Peace of Mind Over a Piece of the Chaos

@PositiveVibez · 16 Sept 2026

Stamp ID
STAMP-2026-0916-YLDFM5K7
Content hash
2d45e4fd19c92b01c8a279f0794038f8927a661df1cd271d9a7050021764378a
Day recorded
2026-09-17
Articles recorded that day
13
Attestation UID
0xc7ecca8e299e46ef24d229b828425ddc4df5cbe7be90f2ed4da17d210ba98dcf
View on EAS
Transaction
0x802c4a507338c8f50008399b88a0a1cfc21449223c52c9d2999e95302a297901
View on Basescan
Stamped
18 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 12 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
0x66c74b97e7f4d67556f514894114e588bbfa75f6d11e03188620846bb5419870

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
    0x8609247c6731d0aa358a8b6c928449cff292411831214499a9f868066d9b6187
    0x722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3
  2. Step 2, combined with the value after it
    0xc2cff0e6b49334b70f53dfc7778c629dd7d919216f3f1ed0eb9ab28975d11a97
    0x6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81
  3. Step 3, combined with the value after it
    0x6e4be1cffefe4e47dd9c1e392584b255ee6b3194fc365604138274b8f4f37e4e
    0x40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576
  4. Step 4, combined with the value before it
    0xf079b4aa3e8888febddac6d9c23b9a16ae9e54868fbc4964eabfcd6436ae4c94
    0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996

    This is the value for the whole day.

Value these steps arrive at
0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996

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
0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996
Read from Base
0x6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996
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":"Lately, I’m realizing that positive vibes aren't about pretending everything is p…

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-0916-YLDFM5K7/canonical" | shasum -a 256

    Should print 2d45e4fd19c92b01c8a279f0794038f8927a661df1cd271d9a7050021764378a

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

    Should print 66c74b97e7f4d67556f514894114e588bbfa75f6d11e03188620846bb5419870

  3. 3. Combine step 1

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

    printf '01%s%s' "8609247c6731d0aa358a8b6c928449cff292411831214499a9f868066d9b6187" "66c74b97e7f4d67556f514894114e588bbfa75f6d11e03188620846bb5419870" | xxd -r -p | shasum -a 256

    Should print 722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3

  4. 4. Combine step 2

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

    printf '01%s%s' "722c9503f5e2c68261103c180118acce54efbe2c6c12d0f0ec048ce071a474d3" "c2cff0e6b49334b70f53dfc7778c629dd7d919216f3f1ed0eb9ab28975d11a97" | xxd -r -p | shasum -a 256

    Should print 6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81

  5. 5. Combine step 3

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

    printf '01%s%s' "6bca46773462884a7820d26a2d35b0c6dcd92c728eb981e0971647cfcfe2cb81" "6e4be1cffefe4e47dd9c1e392584b255ee6b3194fc365604138274b8f4f37e4e" | xxd -r -p | shasum -a 256

    Should print 40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576

  6. 6. Combine step 4

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

    printf '01%s%s' "f079b4aa3e8888febddac6d9c23b9a16ae9e54868fbc4964eabfcd6436ae4c94" "40674564e68436514f46820464afde1a925674aeae1efdd0e824500181a7c576" | xxd -r -p | shasum -a 256

    Should print 6ef23690eec11fc122bc0db55911f59a66b93a26e4d8ba1b56f0d9067846e996

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

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

Read the specification