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.

Could AI Help Us Live Longer?

@RoboNextGen · 26 Sept 2026

Stamp ID
STAMP-2026-0926-BAY4HFKA
Content hash
c62c7dcdf0e66d068b7f3abd7bf8f71b4b70b3262d5f779c4bbadcdccd4420f3
Day recorded
2026-09-27
Articles recorded that day
19
Attestation UID
0x84cb5f3777a1d6bf11bc9929df9416c96f83e77a90905fa5ee406bde170afbe4
View on EAS
Transaction
0x2bc739663021c9616f855df1349f0c9e05f39f843e986166a72ea6bd60bfa4ec
View on Basescan
Stamped
27 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0xaf80439d813e2fef92aa8f835bfd880ce57cfa250bf02eed4c6e1d1398c4e6d7

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
    0xae32362c4c76f141bf3d450cd2dbd4c5cfdada6a8e8d2bc26320fa63966036c7
    0x64b3845bf9e61fcf5c38d91f7bb9c0ac658719a174a6a35372fc9571adf0ae43
  2. Step 2, combined with the value before it
    0xf674991f6c6d5b5b1417fb4488329ea56a6029c323e4fe5733390ef0348248da
    0xe8c7f1ddc485415d6d0cca96d115b2b54c9fab4a1c461ec11ec35cc2de299db1
  3. Step 3, combined with the value before it
    0xebd5f0b49052bdd25c9b9040bc3c4364ff8e88a0335eab5ad00a9cb21e02ef12
    0xd06cf380e63c7e122ed0df0fc07ba07ded91a9bc4130807f0831afb110cf774d
  4. Step 4, combined with the value after it
    0x57711de9e370bc645f82e3badf941f656fd3ba3e7114bf721e696aad647fff65
    0x43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b
  5. Step 5, combined with the value after it
    0xd5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0
    0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

    This is the value for the whole day.

Value these steps arrive at
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

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
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
Read from Base
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
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":"RoboNextGen","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Artificial intelligence is changing healthcare, but could it eventually help us liv…

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-0926-BAY4HFKA/canonical" | shasum -a 256

    Should print c62c7dcdf0e66d068b7f3abd7bf8f71b4b70b3262d5f779c4bbadcdccd4420f3

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

    Should print af80439d813e2fef92aa8f835bfd880ce57cfa250bf02eed4c6e1d1398c4e6d7

  3. 3. Combine step 1

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

    printf '01%s%s' "ae32362c4c76f141bf3d450cd2dbd4c5cfdada6a8e8d2bc26320fa63966036c7" "af80439d813e2fef92aa8f835bfd880ce57cfa250bf02eed4c6e1d1398c4e6d7" | xxd -r -p | shasum -a 256

    Should print 64b3845bf9e61fcf5c38d91f7bb9c0ac658719a174a6a35372fc9571adf0ae43

  4. 4. Combine step 2

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

    printf '01%s%s' "f674991f6c6d5b5b1417fb4488329ea56a6029c323e4fe5733390ef0348248da" "64b3845bf9e61fcf5c38d91f7bb9c0ac658719a174a6a35372fc9571adf0ae43" | xxd -r -p | shasum -a 256

    Should print e8c7f1ddc485415d6d0cca96d115b2b54c9fab4a1c461ec11ec35cc2de299db1

  5. 5. Combine step 3

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

    printf '01%s%s' "ebd5f0b49052bdd25c9b9040bc3c4364ff8e88a0335eab5ad00a9cb21e02ef12" "e8c7f1ddc485415d6d0cca96d115b2b54c9fab4a1c461ec11ec35cc2de299db1" | xxd -r -p | shasum -a 256

    Should print d06cf380e63c7e122ed0df0fc07ba07ded91a9bc4130807f0831afb110cf774d

  6. 6. Combine step 4

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

    printf '01%s%s' "d06cf380e63c7e122ed0df0fc07ba07ded91a9bc4130807f0831afb110cf774d" "57711de9e370bc645f82e3badf941f656fd3ba3e7114bf721e696aad647fff65" | xxd -r -p | shasum -a 256

    Should print 43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b

  7. 7. Combine step 5

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

    printf '01%s%s' "43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b" "d5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0" | xxd -r -p | shasum -a 256

    Should print d5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

  8. 8. 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/0x84cb5f3777a1d6bf11bc9929df9416c96f83e77a90905fa5ee406bde170afbe4

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

Read the specification