The Copperfield Plan
In the crucible of experimentation, we seek to return to first principles—to question the very essence of value, trust, and the nature of economic truth itself.
"Stasis is not preservation—it is entropy disguised as caution. True resilience emerges not from freezing protocols in time, but from understanding how they evolve under pressure."
Our Mission
A Dual Purpose Vision
The Copperfield Plan serves two critical purposes: validating experimental proposals for the Bitcoin community and exploring how Bitcoin's "impossible trinity" of decentralization, security, and scalability may evolve dynamically.
Validation for Bitcoin
Provide a proving ground for technical ideas discussed in the Bitcoin community but not yet adopted into consensus.
Preparation for the Next Era
Explore how Bitcoin's fundamental trade-offs may shift dynamically, rather than remain frozen under extreme conservatism.
Our Philosophy
Bitcoin's durability is built on caution, but progress comes from active exploration. Tondi's Copperfield Plan embraces this role:
Not to compete with Bitcoin, but to act as its wind tunnel—testing how new mechanics behave in live environments.
Not to dilute security, but to generate empirical data that Bitcoin Core and BIP authors can evaluate.
Not to break the trilemma, but to probe how decentralization, scalability, and security trade-offs evolve dynamically.
Focus Areas of Experimentation
Active Implementation of Bitcoin Proposals
| Proposal | Description | Category | Target Version | Status |
|---|---|---|---|---|
| Kaspa-Compatible Payment Types (TSP-0001) | Support Kaspa-Compatible Payment Types with Extended Taproot | Core | v2025a | Implemented |
| BLAKE3 Hash Algorithm (TSP-0002) | Adoption of BLAKE3 Hash Algorithm Across the Tondi Protocol | Core | v2025b | Implemented |
| ASIC-Resistant PoW (TSP-0003) | ASIC-Resistant Proof-of-Work Hash Specification Based on BLAKE3 + Light Memory-Touching | Core | v2026b | Implemented |
| TSP Numbering System (TSP-0004) | Definition of the TSP Numbering, Categories, and Lifecycle | Governance/Meta | v2025a | Implemented |
| Biannual Evolution (TSP-0005) | Biannual Evolution and the Tondi Frontier Network | Governance/Meta | v2025b | Accepted |
| FUN20 (TSP-0006) | Inscription-style fungible token standard (Replaced by Ingot) | Applications | v2025b | Deprecated |
| ANYPREVOUT (TSP-0007) | Enabling eltoo and simplified channel updates | Consensus | v2026a | Review |
| CISA (TSP-0008) | Transaction size reduction via aggregate Schnorr signatures | Consensus | v2026a | Draft |
| CTV (CheckTemplateVerify) (TSP-0009) | Covenant-based transaction commitments | Consensus | v2026b | Draft |
| PTLC (TSP-0010) | Privacy-enhanced conditional payments | Standards Track | v2026a | Implemented |
| Native MuSig2 (TSP-0011) | Efficient multisig aggregation built into consensus rules | Consensus | v2026a | Implemented |
| Channel Factories (TSP-0012) | Multi-party channel construction to reduce on-chain footprint | Layer 2 | v2026b | Draft |
| GhostDAG Sorting Optimization (TSP-0013) | GhostDAG Sorting Optimization Proposal (Local Approximation and Concurrent Data Structures) | Core | v2026b | Draft |
| Native Eltoo and PTLC Layer 2 (TSP-0014) | Native Eltoo transaction types with Point-Time-Locked Contracts for Layer 2 scaling | Consensus / Layer-2 | v2026a | Review |
Opcode Allocation
Tondi Client Opcode Allocation Strategy
The Tondi client reserves specific opcode ranges for different purposes. This allocation ensures compatibility with Bitcoin Taproot while providing space for Tondi-specific features.
| Range | Count | Purpose | Status |
|---|---|---|---|
| 0x00-0x4F | 80 | Basic opcodes (data push, control flow, stack operations) | Implemented |
| 0x50-0x8A | 59 | Extended opcodes (Bitcoin Taproot compatibility + numeric constants + control flow + stack operations + bitwise logic) | Implemented |
| 0x8B-0xA5 | 27 | Numerical operations (arithmetic, comparison, boolean logic) | Implemented |
| 0xA6-0xA7 | 2 | Available for future TSPs | Available |
| 0xA8-0xB1 | 10 | Cryptographic operations (SHA256, BLAKE3, signature verification) | Implemented |
| 0xB2-0xBF | 14 | TSP-allocated | Reserved |
| 0xC0-0xF9 | 58 | Available for future TSPs | Available |
| 0xFA-0xFF | 6 | System reserved opcodes | System |
TSP-Opcode Allocations (0xB2-0xBF)
| Opcode | TSP | Feature | Status |
|---|---|---|---|
| 0xB2-0xB4 | TSP-0007: ANYPREVOUT | OP_CHECKSIG_APO, OP_CHECKSIGVERIFY_APO, OP_CHECKSIGADD_APO | Draft |
| 0xB5-0xB7 | TSP-0008: CISA | OP_CHECKSIG_CISA, OP_CHECKSIGVERIFY_CISA, OP_CHECKSIGADD_CISA | Draft |
| 0xB8 | TSP-0009: CTV | OP_CHECKTEMPLATEVERIFY | Draft |
| 0xB9 | TSP-0012: Channel Factories | OP_CHECKTEMPLATEVERIFY_FACTORY | Draft |
| 0xBA-0xBD | TSP-0011: MuSig2 | OP_MUSIGKEYAGG, OP_MUSIGNONCEAGG, OP_MUSIGPARTIALSIG, OP_MUSIGVERIFY | Implemented |
| 0xBE-0xBF | — | Available for future TSPs | Available |
Rapid Evolution Mechanism
Biannual Upgrade Cycle
The Copperfield Plan implements a biannual evolution mechanism (TSP-0005) that enables rapid protocol upgrades every six months. This allows Tondi to quickly adopt and test new Bitcoin proposals while maintaining network stability.
Evolution Cycle
Every six months, Tondi undergoes a major protocol upgrade, incorporating tested proposals and deprecating obsolete features. This rapid iteration cycle enables continuous innovation while providing real-world validation data.
Benefits of Rapid Evolution
Reporting Back to Bitcoin
Feeding Knowledge Forward
We commit to publishing comprehensive technical reports for ALL tested proposals, providing real-world data, security analysis, attack surface evaluations, and UX implications to Bitcoin Core developers and BIP authors.
Every experiment conducted on Tondi contributes to Bitcoin's collective knowledge. Our findings will be published openly, enabling informed decision-making for Bitcoin's future evolution.
Join the Experiment
Be Part of Bitcoin's Future
Explore the technical specifications, follow our progress, and contribute to the conversation about Bitcoin's next evolution.