Tondi Standard Proposals (TSP)

The Tondi Standard Proposal (TSP) process defines the evolution of the Tondi blockchain and its ecosystem. TSPs are the canonical way to propose, discuss, and standardize protocol-level changes, ecosystem conventions, and governance rules within the Tondi network.

📌 What is a TSP?

A TSP (Tondi Standard Proposal) is a design document that provides information to the Tondi community or describes a new feature for the Tondi chain, its consensus, or its ecosystem. Each TSP should:

Provide a clear technical specification of the change or feature.
Explain the motivation and rationale behind it.
Describe any backward compatibility and security considerations.
Define the implementation and activation plan.

TSPs are the primary mechanism for standardizing the Tondi protocol and ensuring long-term coherence of the ecosystem.

📖 Proposal Workflow

A TSP moves through several stages in its lifecycle:

Draft – Initial version, open for feedback.
Review / Last Call – Under technical review and community discussion.
Accepted – Approved for inclusion in a future Tondi release.
Implemented – Implemented in reference clients and/or testnet.
Final (Active) – Successfully deployed and active on mainnet.
(Optional) Replaced / Deprecated – Superseded by another TSP.

📂 TSP Categories

TSPs are grouped into categories, depending on their scope:

Core – Consensus rules, transaction validation, block structure, cryptography.
Networking – P2P protocols, mempool, synchronization rules.
Applications – Proposals for RGB anchoring, Lexum contracts, AMMs, DAOs, etc.
Layer 2 (L2) – Payment channels, channel factories, off-chain scaling solutions.
Process / Governance – Processes surrounding the TSP workflow and community rules.
Standards / Interface – Wallet formats, RPC APIs, contract schemas, interoperability protocols.
Informational – Research papers, best practices, educational content.

🏷 TSP Numbering System

The TSP numbering system follows a two-phase approach as defined in TSP-0004:

Phase 1: Early TSPs (until October 2025)

Sequential numbering: TSP-0001, TSP-0002, TSP-0003, etc.
Reserved for Genesis Protocol specifications and early ecosystem standards
Current proposals (TSP-0001 through TSP-0012) follow this format

Phase 2: Categorized TSPs (from October 2025 onward)

Proposals will use category prefixes + numeric sequence:

TSP-Cxxx → Core/Consensus (transaction validation, PoW, cryptography)
TSP-Nxxx → Networking (P2P protocols, mempool, synchronization)
TSP-Axxx → Applications (RGB, Lexum contracts, AMMs, DAOs)
TSP-Lxxx → Layer 2 (payment channels, scaling solutions)
TSP-Pxxx → Process/Governance (workflow, voting mechanisms)
TSP-Sxxx → Standards/Interface (wallet formats, APIs, schemas)
TSP-Ixxx → Informational (research papers, best practices)

This ensures both historical continuity and scalability for long-term ecosystem growth.

📋 Current Proposals

Number	Title	Status	Category	Target Version
TSP-0001	Support Kaspa-Compatible Payment Types with Extended Taproot	✅ Implemented	Core	v2025a
TSP-0002	Adoption of BLAKE3 Hash Algorithm Across the Tondi Protocol	✅ Implemented	Core	v2025b
TSP-0003	ASIC-Resistant Proof-of-Work Hash Specification Based on BLAKE3 + Light Memory-Touching	🔄 Review	Core	v2026b
TSP-0004	Definition of the TSP Numbering, Categories, and Lifecycle	✅ Implemented	Governance/Meta	v2025a
TSP-0005	Biannual Evolution and the Tondi Frontier Network	✅ Accepted	Governance/Meta	v2025b
TSP-0006	FUN20 — An Inscription-style Fungible Token Standard for Tondi	🔄 Review	Applications	v2025b
TSP-0007	ANYPREVOUT Support for Eltoo-based Payment Channels (Tondi Flash)	🔄 Review	Consensus	v2026a
TSP-0008	CISA (Cross-Input Signature Aggregation)	📋 Draft	Consensus	v2026a
TSP-0009	CheckTemplateVerify (CTV) Covenant for Tondi	📋 Draft	Consensus	v2026b
TSP-0010	Tondi PTLC (Point Time-Locked Contract) Contract Specification	📋 Draft	Standards Track	v2026a
TSP-0011	Native MuSig2 Multi-Signatures	📋 Draft	Consensus	v2026a
TSP-0012	Channel Factories for Scalable Off-Chain Payment Networks	📋 Draft	Layer 2 (L2)	v2026b
TSP-0013	GhostDAG Sorting Optimization	📋 Draft	Consensus	v2026a
TSP-0014	Native Eltoo and PTLC Layer 2	✅ Implemented	Layer 2 (L2)	v2026a

🔧 Tondi Client Opcode Allocation

The Tondi client reserves specific opcode ranges for different purposes. This allocation ensures compatibility with Bitcoin Taproot while providing space for Tondi-specific features.

Opcode Range Overview

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 opcodes	🔄 Reserved
`0xC0-0xF9`	58	Available for future TSPs	🔄 Available
`0xFA-0xFF`	6	System reserved opcodes	✅ System

TSP-Optcode 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	CheckTemplateVerify (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)	📋 Draft
`0xBE-0xBF`	-	Available for future TSPs	🔄 Available

Future Opcode Space

Short-term: 2 opcodes (0xBE-0xBF) for urgent fixes or small features
Medium-term: 2 opcodes (0xA6-0xA7) for special functionality
Long-term: 58 opcodes (0xC0-0xF9) for large-scale features and complex protocols

Total available opcodes: 62 (2 + 2 + 58)

✍️ How to Propose a TSP

Fork this repository.
Create a new file under /tsp named tsp-xxxx.md, where xxxx is your draft number.
Write the TSP using the official TSP Template.
Submit a Pull Request.
The TSP editors and the community will review and assign an official number.

📜 License

All TSP documents are licensed under CC0 1.0 Universal (Public Domain Dedication).