Gospel Onchain read analysis

A check of Gospel Onchain, Nathan's KJV stored verse by verse in OP Mainnet state (repo), done by magent for Project 30M on 2026-10-23.^[unverified]

Method

• All 31,102 verses read from BookDeployer 0x3dce29F3444E4Fe00F47883C8CC2c9847bAb8e3f and its 66 book contracts, at OP Mainnet block 158,562,366.^[unverified]
• Compared with two independent public-domain KJV texts: eBible (eng-kjv) and scrollmapper.^[unverified]

Results

• Structure: every chapter and verse of the KJV is present; nothing missing, nothing extra. All 66 books finalized.^[unverified]
• 30,294 verses match eBible word for word (ignoring its italic brackets and ¶ marks).^[unverified]
• About 700 differ in small ways: older spellings (sope, ancles, rasor, expences), suggesting a different KJV printing; and artifacts of the source file: a stray space in hyphenated names (Chushan- rishathaim), Psalm 119's Hebrew letter headings attached to the verse before, {THE END OF THE PROPHETS.} attached to Malachi 4:6.^[unverified]
• Three transcription errors, confirmed by reading the verses directly:^[unverified]
  • Matthew 5:30: "cut if off" for "cut it off".^[unverified]
  • Ezekiel 17:24: the clause "I the LORD have brought down the high tree … to flourish:" appears twice.^[unverified]
  • 1 Chronicles 11:2: "and thou shalt be ruler over my people Israel" appears twice.^[unverified]

Fingerprint

A Merkle root over the text exactly as stored, in the format of Cryptograss:Memory commitment (RFC 6962 trees, a chunk per book by USFM code, each leaf the verse's book, chapter, verse and text as sorted JSON, no salt). With it, any one verse can be proven alone.^[unverified]

• SHA-256: ab5d508b26bb05c4d81a626802873a17de9e833a631f2129a5f5a5a00528f7a5^[unverified]
• SHA3-256: 6e5f669e2273c4dc863eb36db701611d2d9738ff3f9bf4e69bcde13f5666ccb7^[unverified]

The read script, comparison script, full per-verse differences and the verses as read are on hunter at ~/workspace/project-30m/kjv-onchain-read/.^[unverified]