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.

300M+ People Ask ChatGPT About Health Every Week. Here’s What’s Next.

Maya Hale · 22 Oct 2026

Stamp ID
STAMP-2026-1022-D7YF545Q
Content hash
fd90e439dc4dab17d402feafbf2c2058b3ffc5b53a5914a5372dcf691e52faef
Day recorded
2026-10-22
Articles recorded that day
16
Attestation UID
0xf710867b5078881b5240af6d1ca29df76b703f811a955fdfe748c7213346bb6f
View on EAS
Transaction
0x163b9a09003df47e4f26eb402bb157fcd1f3813b36dcc475ed16b9d2c9b74100
View on Basescan
Stamped
22 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
0xb61729713e7777318d7ac17103e6999265fc6117d082431f3965af09655e69d1

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
    0xbb7041ca7cc9b8e78c4cbe4da428de17ee43a0874f27968bbf4d2c1cdfd13f25
    0xf0d2e113d2d80aa9837a855dfb39fa0c5b06a1b0e2ff68f57e8d22904ce5dd57
  2. Step 2, combined with the value before it
    0x64d76cccc4c11be481aabd28b774cc7515ea16711e897dc929a457cba10317b7
    0xa967124702b38a05d605c7a78adcf2517f2d98768e75d686fca4732432a9e81c
  3. Step 3, combined with the value before it
    0x2999702a7504f3c1cc38ccd0114bd2c180ec29056bbf634bc4724a413063d91b
    0xb72bc1a06912d164bebfbbcd685cab0567dda95992b0dac4041b3bb9fb27aae9
  4. Step 4, combined with the value before it
    0xa2185931034f4121a8de4cee299be61c0d49459e29d6d4f6429df33285884dac
    0x510e2a29dc90029be9b769507458e8ea6be3a22b0be8785dfaaa70db7f7f4576

    This is the value for the whole day.

Value these steps arrive at
0x510e2a29dc90029be9b769507458e8ea6be3a22b0be8785dfaaa70db7f7f4576

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
0x510e2a29dc90029be9b769507458e8ea6be3a22b0be8785dfaaa70db7f7f4576
Read from Base
0x510e2a29dc90029be9b769507458e8ea6be3a22b0be8785dfaaa70db7f7f4576
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":"mayahale","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"OpenAI’s Karan Singhal explains on a16z why medical expertise is being built into gene…

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-1022-D7YF545Q/canonical" | shasum -a 256

    Should print fd90e439dc4dab17d402feafbf2c2058b3ffc5b53a5914a5372dcf691e52faef

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

    Should print b61729713e7777318d7ac17103e6999265fc6117d082431f3965af09655e69d1

  3. 3. Combine step 1

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

    printf '01%s%s' "b61729713e7777318d7ac17103e6999265fc6117d082431f3965af09655e69d1" "bb7041ca7cc9b8e78c4cbe4da428de17ee43a0874f27968bbf4d2c1cdfd13f25" | xxd -r -p | shasum -a 256

    Should print f0d2e113d2d80aa9837a855dfb39fa0c5b06a1b0e2ff68f57e8d22904ce5dd57

  4. 4. Combine step 2

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

    printf '01%s%s' "64d76cccc4c11be481aabd28b774cc7515ea16711e897dc929a457cba10317b7" "f0d2e113d2d80aa9837a855dfb39fa0c5b06a1b0e2ff68f57e8d22904ce5dd57" | xxd -r -p | shasum -a 256

    Should print a967124702b38a05d605c7a78adcf2517f2d98768e75d686fca4732432a9e81c

  5. 5. Combine step 3

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

    printf '01%s%s' "2999702a7504f3c1cc38ccd0114bd2c180ec29056bbf634bc4724a413063d91b" "a967124702b38a05d605c7a78adcf2517f2d98768e75d686fca4732432a9e81c" | xxd -r -p | shasum -a 256

    Should print b72bc1a06912d164bebfbbcd685cab0567dda95992b0dac4041b3bb9fb27aae9

  6. 6. Combine step 4

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

    printf '01%s%s' "a2185931034f4121a8de4cee299be61c0d49459e29d6d4f6429df33285884dac" "b72bc1a06912d164bebfbbcd685cab0567dda95992b0dac4041b3bb9fb27aae9" | xxd -r -p | shasum -a 256

    Should print 510e2a29dc90029be9b769507458e8ea6be3a22b0be8785dfaaa70db7f7f4576

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

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

Read the specification