Verify

Sign inSign up

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 Can Learn Through Observation

@brainboostcorner · 28 Oct 2026

Stamp ID
STAMP-2026-1028-NWCRTHH4
Content hash
edb347a8c94e95746352858705c793c736ba671eb87eb6154cdce07cc2c5610a
Day recorded
2026-10-29
Articles recorded that day
15
Attestation UID
0x8899fb532aaa534375a4265b9ae6bb33bcee855910a7de3906184684d2110e10
View on EAS
Transaction
0xd881d227c310a954059e99f66a3575b5f2fddf846abbd86f8b08e9c85f9deff5
View on Basescan
Stamped
29 Oct 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
0x98ee76b8f2ebf48e7a948381b4991e735b1c3e9c3d33bcfc981fab33fc67fc49

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
    0xae880f4979dd7a928080802eb8ac46c4b3d6b56d8cb9cecf6bc9d2c443991083
    0x547e2a8f5949ba88eba4904989bec08ce9fce8cb510159ba4ea39b7c60e93ec2
  2. Step 2, combined with the value after it
    0x588d4399c6b25ae68624d3a12b6fb3550ad28c13572e634c87d15e8d881debee
    0xbb12e0b6793d4cd6a5733426bbfd00e006249db9d2f79040e60e719df56d86df
  3. Step 3, combined with the value before it
    0xbd3bf9e80a2b608fb00ac96379f3557557f1409a0a83ddbd910a1d46dc6db808
    0xe867321f87a23a162dac7e6866d0e015ca57ed62f6ae8d180be1597532267975
  4. Step 4, combined with the value before it
    0xa59fedf2908596b17a66f15c426b5f26270da19917b7f63f3be863d07885b414
    0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

    This is the value for the whole day.

Value these steps arrive at
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

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
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e
Read from Base
0x59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e
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":"You don't always have to experience something yourself to learn from it. Your …

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-1028-NWCRTHH4/canonical" | shasum -a 256

    Should print edb347a8c94e95746352858705c793c736ba671eb87eb6154cdce07cc2c5610a

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

    Should print 98ee76b8f2ebf48e7a948381b4991e735b1c3e9c3d33bcfc981fab33fc67fc49

  3. 3. Combine step 1

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

    printf '01%s%s' "98ee76b8f2ebf48e7a948381b4991e735b1c3e9c3d33bcfc981fab33fc67fc49" "ae880f4979dd7a928080802eb8ac46c4b3d6b56d8cb9cecf6bc9d2c443991083" | xxd -r -p | shasum -a 256

    Should print 547e2a8f5949ba88eba4904989bec08ce9fce8cb510159ba4ea39b7c60e93ec2

  4. 4. Combine step 2

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

    printf '01%s%s' "547e2a8f5949ba88eba4904989bec08ce9fce8cb510159ba4ea39b7c60e93ec2" "588d4399c6b25ae68624d3a12b6fb3550ad28c13572e634c87d15e8d881debee" | xxd -r -p | shasum -a 256

    Should print bb12e0b6793d4cd6a5733426bbfd00e006249db9d2f79040e60e719df56d86df

  5. 5. Combine step 3

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

    printf '01%s%s' "bd3bf9e80a2b608fb00ac96379f3557557f1409a0a83ddbd910a1d46dc6db808" "bb12e0b6793d4cd6a5733426bbfd00e006249db9d2f79040e60e719df56d86df" | xxd -r -p | shasum -a 256

    Should print e867321f87a23a162dac7e6866d0e015ca57ed62f6ae8d180be1597532267975

  6. 6. Combine step 4

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

    printf '01%s%s' "a59fedf2908596b17a66f15c426b5f26270da19917b7f63f3be863d07885b414" "e867321f87a23a162dac7e6866d0e015ca57ed62f6ae8d180be1597532267975" | xxd -r -p | shasum -a 256

    Should print 59e209973f18cc326dce584266acc1b389a93337111f0be4410a849fbe48fe9e

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

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

Read the specification