← Back to Reader

BIBLE1 Protocol

// Immutable Text Storage on the BSV Blockchain

Abstract

BIBLE1 is an application-layer protocol for storing structured text documents permanently on the BSV blockchain. The protocol enables books, manuscripts, and literary works to be inscribed on-chain with a hierarchical index system, allowing complete works to be accessed via a single transaction ID.

The reference implementation includes the complete King James Bible with Apocrypha and the German Lutherbibel 1912—demonstrating the protocol's capability for multi-language scripture storage. Combined: 146 books, 2,551 chapters, and 67,924 verses for approximately $1.05 USD in transaction fees.

Problem Statement

Published content faces three fundamental threats in the digital age:

• Censorship — Platforms, governments, and corporations can remove content at will. Books are banned, articles are deleted, and history is rewritten.
• Platform Dependency — Content hosted on centralized services disappears when companies fail, change policies, or choose to deplatform creators.
• Mutability — Digital texts can be silently altered. There is no guarantee that what you read today matches what was originally published.

The historical precedent is clear: in 1825, Protestant publishers removed 14 books from the Bible—the Apocrypha—without broad public consent. These books, present in Christian scripture for over 1,500 years, were simply deleted from future printings.

Solution Architecture

BIBLE1 uses a two-tier storage model:

Content Layer

Each chapter or section is stored as an individual transaction with an OP_RETURN output containing:

• Protocol identifier: BIBLE1
• JSON payload with book name, chapter number, and verse array

Index Layer

A master index transaction contains a JSON object mapping every chapter key to its transaction ID. This single "master txId" provides access to the entire work.

Technical Specification

Transaction Format

Standard BSV transactions with two outputs:

• Output 0: OP_RETURN with protocol prefix and JSON payload
• Output 1: P2PKH change output (if applicable)

Content Record Structure

Field	Type	Description
protocol	string	"BIBLE1" identifier
book	string	Book name (e.g., "Genesis")
chapter	integer	Chapter number
verses	array	Array of verse strings

Index Record Structure

The master index is a JSON object where keys are {Book}_{Chapter} and values are transaction IDs:

{
  "Genesis_1": "282bf8d6dd543b9573e0c47bec3bc1c4...",
  "Genesis_2": "a1b2c3d4e5f6...",
  ...
  "Revelation_22": "ffe41b344fd166928ddb4594c32ef433..."
}

Cryptographic Verification

Every BIBLE1 transaction is secured by Bitcoin's cryptographic infrastructure:

Merkle Tree Integration

Each transaction is hashed and included in the block's Merkle tree—a binary tree structure where each leaf node is a transaction hash, and each non-leaf node is the hash of its children. The Merkle root, included in the block header, cryptographically commits to every transaction in the block.

This means any alteration to a single verse would change the transaction hash, which would change the Merkle root, which would invalidate the block header's proof-of-work. Tampering is mathematically impossible without re-mining the entire blockchain from that point forward.

SHA-256 Double Hashing

Transaction IDs are computed as SHA256(SHA256(raw_tx)), providing 256-bit collision resistance. The probability of two different texts producing the same txId is approximately 1 in 2²⁵⁶—effectively zero.

Proof of Inclusion

Any transaction can be verified against the block header using a Merkle proof—a compact path of hashes from the transaction to the Merkle root. This allows lightweight clients to verify content authenticity without downloading the entire blockchain.

Content Retrieval

Reading content from the blockchain requires:

1. Fetch master index transaction from any BSV node or API
2. Parse JSON to get chapter-to-txId mapping
3. Fetch individual chapter transactions as needed
4. Parse OP_RETURN data to extract verses

The reference viewer at bsvbible.club implements this flow using the WhatsOnChain API, with local caching for performance.

Read via Command Line

The Bible can be read directly from the blockchain without any website. We provide scripts for all platforms that fetch and decode scripture directly from BSV transactions.

PowerShell (Windows)

Download: read-bible.ps1 | View on GitHub Gist

# Read John chapter 3
.\read-bible.ps1 "John" 3

# Read Genesis chapter 1
.\read-bible.ps1 "Genesis" 1

# List all available books
.\read-bible.ps1 -ListBooks

# Output raw JSON from blockchain
.\read-bible.ps1 "Psalms" 23 -Raw

Bash (Linux/Mac)

Download: read-bible.sh | View on GitHub Gist

Requires: curl, jq, xxd

# Make executable
chmod +x read-bible.sh

# Read John chapter 3
./read-bible.sh "John" 3

# Read Genesis chapter 1
./read-bible.sh "Genesis" 1

# List all available books
./read-bible.sh --list-books

One-Liner (Any Platform with curl)

Fetch John 3:16's chapter directly from the blockchain:

curl -s "https://api.whatsonchain.com/v1/bsv/main/tx/e8e94760404a997e2c0743db12bff23826839b67c399bb9c165ebdd32394c69b" | \
  jq -r '.vout[] | select(.value==0) | .scriptPubKey.hex' | \
  xxd -r -p | tail -c +8 | jq '.verses[15]'

Output: "For God so loved the world, that he gave his only begotten Son..."

How It Works

1. Scripts fetch the chapter index (maps book/chapter to transaction ID)
2. Look up the transaction ID for the requested chapter
3. Fetch the raw transaction from the WhatsOnChain API
4. Decode the OP_RETURN hex data to UTF-8
5. Parse the JSON and display verses

Multi-Language Support

BIBLE1 supports multiple Bible translations in different languages. Each translation has its own master index transaction, allowing independent verification and access.

Translation	Language	Books	Chapters	Verses	Cost
King James Version + Apocrypha	English	80	1,362	36,822	~$0.75
Lutherbibel 1912	German	66	1,189	31,102	~$0.30

Planned translations: Spanish (Reina-Valera 1909), French (Louis Segond 1910), Portuguese, Chinese, Arabic, and more. Community contributions welcome.

Economics

BSV's low transaction fees make large-scale text storage economically viable:

Metric	Value
Total transactions	1,363 (1,362 chapters + 1 index)
Total data stored	~4.5 MB
Fee rate	~0.5 sat/byte
Total cost	~$0.75 USD
Cost per chapter	~$0.00055

Guarantees

• Immutability: Once confirmed, transactions cannot be altered or reversed
• Availability: Data is replicated across all BSV nodes globally
• Verifiability: Anyone can independently verify content by txId
• Permanence: Content persists as long as the BSV network exists
• Censorship Resistance: No single entity can remove on-chain data

Future Development

The BIBLE1 protocol serves as the foundation for a broader publishing platform:

• Commit Tool: Web interface for uploading and inscribing documents
• Universal Viewer: Reader application supporting QR code scanning for instant access
• Public Gallery: Directory of on-chain publications indexed by creator address
• Multi-format Support: Import from TXT, MD, DOCX, PDF, EPUB

Conclusion

BIBLE1 demonstrates that meaningful, large-scale document storage on the blockchain is not only possible but economically practical. For less than a dollar, an entire religious text spanning thousands of years of human history has been preserved in a form that cannot be censored, altered, or destroyed.

This is the promise of Bitcoin fulfilled—not as a speculative asset, but as a utility for permanent, verifiable information storage.

// The Word made chain.

---

BSV Bible — bsvbible.club
Master Index: cf53cae0cf36ffe8333c7ada3416e897ae8ff11d6acc7c1905cabd725a089157
Wallet: 1KKsXhTHx6cSPF7iq5dGQSt6Rz7vBq32yB
⚠ This wallet is for publishing only. Do not send BSV to this address.