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 joy

@PositiveVibez · 18 Sept 2026

Stamp ID
STAMP-2026-0918-3NFQASXB
Content hash
7d10b5f7a6c9be8efdd67d1433cd096dbdd7566fccaf9515be06da0fda933d7d
Day recorded
2026-09-19
Articles recorded that day
15
Attestation UID
0xc48bcdaed99a48da29d734b69296d6330e0615c96d1384813677657a4f8d3d81
View on EAS
Transaction
0x12fc338f9a8535386d71a005752fe80f728ee3d4b7106c34514c764ca2057f9b
View on Basescan
Stamped
20 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 14 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
0x9c9723803b719452dce3040ed67f343e2a3810b5e611c7f219c136ac4776b062

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
    0x5e0e669ea5d316fb87ff1985690fbe8eae6448cc78917b8318d049f0b98df0fe
    0x9f7659d8c8673e48bb0571c9c25abbc0e8dd7e914de557226756eb64c45b745a
  2. Step 2, combined with the value after it
    0x46e229bdef6870bc5c9c1d4c4b0b3753cf4c13fa77c2f0daf3f5eff062b478f8
    0x5512aa4312e44cbfe6e606916bb88ed9c0dd69d90e820e16efed750edb411931
  3. Step 3, combined with the value after it
    0xb0a7aee5bd0ae5aab080adebbc503b312924644ee2a68b83a48581878ede5d18
    0x4129c5ad64d926f37c538109754f0e9263f89c02ced93bdd213ba4405e4e9531
  4. Step 4, combined with the value after it
    0x515b55281df5784e98cbad465386a2275a74de0c9ea58616bb751482c219f11d
    0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

    This is the value for the whole day.

Value these steps arrive at
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

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
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f
Read from Base
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f
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":[{"attrs":{"alt":"choose joy","src":"https://media.vitahash.org/articles/253f1f57-4320-4210-afb3-3e1665…

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-0918-3NFQASXB/canonical" | shasum -a 256

    Should print 7d10b5f7a6c9be8efdd67d1433cd096dbdd7566fccaf9515be06da0fda933d7d

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

    Should print 9c9723803b719452dce3040ed67f343e2a3810b5e611c7f219c136ac4776b062

  3. 3. Combine step 1

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

    printf '01%s%s' "5e0e669ea5d316fb87ff1985690fbe8eae6448cc78917b8318d049f0b98df0fe" "9c9723803b719452dce3040ed67f343e2a3810b5e611c7f219c136ac4776b062" | xxd -r -p | shasum -a 256

    Should print 9f7659d8c8673e48bb0571c9c25abbc0e8dd7e914de557226756eb64c45b745a

  4. 4. Combine step 2

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

    printf '01%s%s' "9f7659d8c8673e48bb0571c9c25abbc0e8dd7e914de557226756eb64c45b745a" "46e229bdef6870bc5c9c1d4c4b0b3753cf4c13fa77c2f0daf3f5eff062b478f8" | xxd -r -p | shasum -a 256

    Should print 5512aa4312e44cbfe6e606916bb88ed9c0dd69d90e820e16efed750edb411931

  5. 5. Combine step 3

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

    printf '01%s%s' "5512aa4312e44cbfe6e606916bb88ed9c0dd69d90e820e16efed750edb411931" "b0a7aee5bd0ae5aab080adebbc503b312924644ee2a68b83a48581878ede5d18" | xxd -r -p | shasum -a 256

    Should print 4129c5ad64d926f37c538109754f0e9263f89c02ced93bdd213ba4405e4e9531

  6. 6. Combine step 4

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

    printf '01%s%s' "4129c5ad64d926f37c538109754f0e9263f89c02ced93bdd213ba4405e4e9531" "515b55281df5784e98cbad465386a2275a74de0c9ea58616bb751482c219f11d" | xxd -r -p | shasum -a 256

    Should print 5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

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

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

Read the specification