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.

What Actually Helps Protect Cognitive Function?

@brainboostcorner · 6 Oct 2026

Stamp ID
STAMP-2026-1006-M4I2ESST
Content hash
a4f14294417a5ad388b868735cecf75f045da61d4ad397b4d30e43857a50a502
Day recorded
2026-10-07
Articles recorded that day
16
Attestation UID
0x2838e247dcdc03d7e5d3def4582bb14c0fd666fbfbca325ed921536c8267f446
View on EAS
Transaction
0x70789bf19e02a7f6c3d6d64f551810889fee56d00e65909f037a2b329b146784
View on Basescan
Stamped
7 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
0xa0eeb785e39d7726e1f614f79bf3f8fe07b49e218ade94ac03e576534e787695

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
    0x78a51fef4872f0c890a1455d8a61171e7933ae86eee098a2016f953e26bca22b
    0x71effab7a48c70daeb71ac024995bf4a3fefb2117b51b8a98af3dededdbd1cca
  2. Step 2, combined with the value after it
    0x538516a36adb7f32ea6df31469186672dd741c336c3c7d02bc5075afaf21c5d2
    0xb54fc78079cf370c2062960424dc717bec7cbc877726a66bea6b0bc364e9eca0
  3. Step 3, combined with the value after it
    0xd5b9b4566485f5e1f6b2b59ab8e5516516b2fc730f99ea98521b18bb5d9f3100
    0xf7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4
  4. Step 4, combined with the value before it
    0x531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5
    0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

    This is the value for the whole day.

Value these steps arrive at
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

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
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07
Read from Base
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07
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":"Keeping your brain sharp isn’t about one magic supplement or a single “brain f…

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-1006-M4I2ESST/canonical" | shasum -a 256

    Should print a4f14294417a5ad388b868735cecf75f045da61d4ad397b4d30e43857a50a502

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

    Should print a0eeb785e39d7726e1f614f79bf3f8fe07b49e218ade94ac03e576534e787695

  3. 3. Combine step 1

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

    printf '01%s%s' "78a51fef4872f0c890a1455d8a61171e7933ae86eee098a2016f953e26bca22b" "a0eeb785e39d7726e1f614f79bf3f8fe07b49e218ade94ac03e576534e787695" | xxd -r -p | shasum -a 256

    Should print 71effab7a48c70daeb71ac024995bf4a3fefb2117b51b8a98af3dededdbd1cca

  4. 4. Combine step 2

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

    printf '01%s%s' "71effab7a48c70daeb71ac024995bf4a3fefb2117b51b8a98af3dededdbd1cca" "538516a36adb7f32ea6df31469186672dd741c336c3c7d02bc5075afaf21c5d2" | xxd -r -p | shasum -a 256

    Should print b54fc78079cf370c2062960424dc717bec7cbc877726a66bea6b0bc364e9eca0

  5. 5. Combine step 3

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

    printf '01%s%s' "b54fc78079cf370c2062960424dc717bec7cbc877726a66bea6b0bc364e9eca0" "d5b9b4566485f5e1f6b2b59ab8e5516516b2fc730f99ea98521b18bb5d9f3100" | xxd -r -p | shasum -a 256

    Should print f7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4

  6. 6. Combine step 4

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

    printf '01%s%s' "531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5" "f7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4" | xxd -r -p | shasum -a 256

    Should print fd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

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

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

Read the specification