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.

Your brain loves a little uncertainty.

@brainboostcorner · 7 Oct 2026

Stamp ID
STAMP-2026-1007-V42YXUFE
Content hash
aaec36c48df35849cb24cdd1dd8ed557c36c1a5a70878ad17aaa672bd2184e95
Day recorded
2026-10-08
Articles recorded that day
16
Attestation UID
0x3fd72ca76c79be099aa7f432c6fb16edc08982e9c7ef6528aa816dccff3b4ac8
View on EAS
Transaction
0x3379a1fcacf0777d45b279ac455541dcaee6ec6fdf7c604fb5a904496de0a459
View on Basescan
Stamped
8 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
0xc01c793e6bfbe34fe81fff0027da434c415cd34d9af0b342d760006c34ec52c0

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
    0xce04bb68e4411c9ecefa782ddb4cf80e4dfc79fa1ef0d91b6208b0f4c749bb5e
    0x310f6b621178237bacdf4e9a1ce64aefa2015de71b637956e7af841d3fcabea2
  2. Step 2, combined with the value after it
    0xc6622403d80b8950dcb07340a05938f79a81f1a08c88124c6500761371e658f6
    0x4537175538c44e573b2d90a61b0f598825979e92817c405e566f6a36f8acfebb
  3. Step 3, combined with the value before it
    0x5cb2d673167ef145af0ede685e176693b233ed2ce3c18dbf26bd7b31bec42a63
    0x4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787
  4. Step 4, combined with the value before it
    0x21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823
    0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

    This is the value for the whole day.

Value these steps arrive at
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
Read from Base
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
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":"brainboostcorner","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Doing the same things the same way every day keeps your brain on autopilot. Tr…

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-1007-V42YXUFE/canonical" | shasum -a 256

    Should print aaec36c48df35849cb24cdd1dd8ed557c36c1a5a70878ad17aaa672bd2184e95

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

    Should print c01c793e6bfbe34fe81fff0027da434c415cd34d9af0b342d760006c34ec52c0

  3. 3. Combine step 1

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

    printf '01%s%s' "ce04bb68e4411c9ecefa782ddb4cf80e4dfc79fa1ef0d91b6208b0f4c749bb5e" "c01c793e6bfbe34fe81fff0027da434c415cd34d9af0b342d760006c34ec52c0" | xxd -r -p | shasum -a 256

    Should print 310f6b621178237bacdf4e9a1ce64aefa2015de71b637956e7af841d3fcabea2

  4. 4. Combine step 2

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

    printf '01%s%s' "310f6b621178237bacdf4e9a1ce64aefa2015de71b637956e7af841d3fcabea2" "c6622403d80b8950dcb07340a05938f79a81f1a08c88124c6500761371e658f6" | xxd -r -p | shasum -a 256

    Should print 4537175538c44e573b2d90a61b0f598825979e92817c405e566f6a36f8acfebb

  5. 5. Combine step 3

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

    printf '01%s%s' "5cb2d673167ef145af0ede685e176693b233ed2ce3c18dbf26bd7b31bec42a63" "4537175538c44e573b2d90a61b0f598825979e92817c405e566f6a36f8acfebb" | xxd -r -p | shasum -a 256

    Should print 4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787

  6. 6. Combine step 4

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

    printf '01%s%s' "21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823" "4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787" | xxd -r -p | shasum -a 256

    Should print 4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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

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

Read the specification