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.

Claude Discovers a Possible New Gene-Editing Mechanism

Chayakrit Krittanawong, MD, FACC, FAHA, FSCAI · 23 Sept 2026

Stamp ID
STAMP-2026-0923-BGLNSKKA
Content hash
69f527032965215a01120ee4b712a5c4e13bf47cfff98f87c69086e4e8fd7440
Day recorded
2026-09-24
Articles recorded that day
17
Attestation UID
0x762e6311ed34312a3f3132a6182a8042fbfb824a36d9ae6d78578c9b6b802645
View on EAS
Transaction
0xe6f94b9a91b705afc7d83ce1a42a74215dde7d1a18a31b24220210388e2cdc0a
View on Basescan
Stamped
24 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 16 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
0xe4a7cbfb6b095e479f134e454dc73c6be38c14400daada2674384bcfbf809fa5

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
    0xb25cf2bfaa9dd30c4cd791629397beff8aa1bfebbab2d3b249157916f332de6f
    0x7790a67988c95e9ddb4277f0485103aa222f39db1dd580614f4b6fabc2eb07d8
  2. Step 2, combined with the value after it
    0x8637afac44d022b9291e32ec35adaefc8e51cb12963da94e2e3853c7a9dcf72d
    0x810a0b87471478bacdd40b4ec2941408a4bfd4a2d74f3ee06b6f74191b567cf1
  3. Step 3, combined with the value before it
    0x0f4cdf5e49c3556651293c95b323d3c9c6b081975eaafbd69902f50918a03467
    0x580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44
  4. Step 4, combined with the value after it
    0x7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39
    0xcc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26
  5. Step 5, combined with the value after it
    0x84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d
    0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

    This is the value for the whole day.

Value these steps arrive at
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

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
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec
Read from Base
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec
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":"Drkrittanawong","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Today, Anthropic announced the Claude-led discovery of a molecular machine that …

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-0923-BGLNSKKA/canonical" | shasum -a 256

    Should print 69f527032965215a01120ee4b712a5c4e13bf47cfff98f87c69086e4e8fd7440

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

    Should print e4a7cbfb6b095e479f134e454dc73c6be38c14400daada2674384bcfbf809fa5

  3. 3. Combine step 1

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

    printf '01%s%s' "b25cf2bfaa9dd30c4cd791629397beff8aa1bfebbab2d3b249157916f332de6f" "e4a7cbfb6b095e479f134e454dc73c6be38c14400daada2674384bcfbf809fa5" | xxd -r -p | shasum -a 256

    Should print 7790a67988c95e9ddb4277f0485103aa222f39db1dd580614f4b6fabc2eb07d8

  4. 4. Combine step 2

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

    printf '01%s%s' "7790a67988c95e9ddb4277f0485103aa222f39db1dd580614f4b6fabc2eb07d8" "8637afac44d022b9291e32ec35adaefc8e51cb12963da94e2e3853c7a9dcf72d" | xxd -r -p | shasum -a 256

    Should print 810a0b87471478bacdd40b4ec2941408a4bfd4a2d74f3ee06b6f74191b567cf1

  5. 5. Combine step 3

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

    printf '01%s%s' "0f4cdf5e49c3556651293c95b323d3c9c6b081975eaafbd69902f50918a03467" "810a0b87471478bacdd40b4ec2941408a4bfd4a2d74f3ee06b6f74191b567cf1" | xxd -r -p | shasum -a 256

    Should print 580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44

  6. 6. Combine step 4

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

    printf '01%s%s' "580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44" "7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39" | xxd -r -p | shasum -a 256

    Should print cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26

  7. 7. Combine step 5

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

    printf '01%s%s' "cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26" "84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d" | xxd -r -p | shasum -a 256

    Should print 0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

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

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

Read the specification