TSP-0004 Categorization

This proposal defines the Tondi Standard Proposal (TSP) numbering system, categorization, and lifecycle process

Proposal Number: TSP-0004
Proposal Name: TSP Numbering and Categorization Specification
Proposal Status: Draft
Author: Tondi Foundation Development Team
Creation Date: 2025-05-05
Protocol Scope: Meta-process (proposal workflow, numbering, and governance rules)

๐Ÿ” Overview

This proposal defines the Tondi Standard Proposal (TSP) numbering system, categorization, and lifecycle process. It establishes a clear framework for how proposals are written, reviewed, accepted, and archived.

Specifically, it introduces two numbering phases:

  1. Pre-October 2025 โ†’ Sequential numbering with format TSP-000x.
  2. Post-October 2025 โ†’ Categorized numbering scheme modeled after Bitcoinโ€™s BIP and Ethereumโ€™s EIP classification.

This ensures both historical continuity (early proposals remain simple and sequential) and scalability (future proposals are organized by domain).

๐ŸŽฏ Goals

  • Provide a consistent and transparent numbering convention for TSPs;
  • Categorize proposals by domain (consensus, networking, applications, governance, informational);
  • Define the lifecycle stages of a TSP, from draft to final;
  • Clarify editorial responsibilities and community governance of the process;
  • Ensure Tondiโ€™s proposal system can scale to long-term ecosystem growth.

๐Ÿ”ข Numbering Rules

Phase 1: Early TSPs (until October 2025)

  • Proposals use sequential 4-digit numbering: TSP-0001, TSP-0002, โ€ฆ

  • Reserved for Genesis Protocol specifications and early ecosystem standards.

  • Examples:

    • TSP-0001 โ†’ Kaspa-compatible + Taproot support
    • TSP-0002 โ†’ BLAKE3 as unified hash function
    • TSP-0003 โ†’ ASIC-resistant PoW with memory-touch randomness

Phase 2: Categorized TSPs (from October 2025 onward)

Proposals must include a category prefix + numeric sequence:

  • TSP-Cxxx โ†’ Core / Consensus

    • Transaction validation rules
    • Proof-of-Work algorithms
    • Block structure
    • Cryptography primitives

  • TSP-Nxxx โ†’ Networking

    • P2P protocols
    • Gossip/mempool rules
    • DAG synchronization mechanisms

  • TSP-Axxx โ†’ Applications

    • RGB anchoring
    • Lexum smart contracts
    • AMM, DAO frameworks
    • Token standards and protocols

  • TSP-Lxxx โ†’ Layer 2 (L2)

    • Payment channels and state channels
    • Channel factories and multi-party protocols
    • Off-chain scaling solutions
    • Layer-2 interoperability and bridges

  • TSP-Pxxx โ†’ Process / Governance

    • TSP workflow and lifecycle definitions
    • On-chain/off-chain governance
    • Voting mechanisms and federation rules

  • TSP-Sxxx โ†’ Standards / Interface

    • Wallet formats and standards
    • RPC APIs and interfaces
    • Contract schemas and formats
    • Interoperability protocols

  • TSP-Ixxx โ†’ Informational

    • Explanatory or research papers
    • Non-consensus guidelines
    • Best practices for developers
    • Educational content and tutorials

๐Ÿ”„ Lifecycle Stages

A TSP progresses through the following statuses:

  1. Draft โ€“ The initial proposal, open for feedback.
  2. Review / Last Call โ€“ Under technical review and community discussion.
  3. Accepted โ€“ Approved for inclusion in a future Tondi release.
  4. Implemented โ€“ Implemented in reference clients and/or testnet.
  5. Final (Active) โ€“ Successfully deployed and active on mainnet.
  6. Replaced / Deprecated (optional) โ€“ Superseded by another TSP but retained for history.

โš–๏ธ Governance & Editorial Process

  • Editors: The Tondi Foundation appoints a set of TSP editors responsible for numbering, formatting, and maintaining consistency.
  • Community Review: Drafts are published publicly for discussion and may move forward only after a community review period (minimum 2 weeks).
  • Acceptance: Final authority for acceptance lies with the Tondi Foundation governance committee, though technical consensus is required.
  • Archival: Finalized TSPs are immutable and archived for permanent reference.

๐Ÿ“ Additional Notes

  • All TSPs must be written in Markdown and submitted via pull requests to the official repository.
  • Each TSP must follow the TSP Template.
  • Licensing: All TSPs are published under CC0 1.0 Universal (Public Domain Dedication).

๐Ÿ“Œ Conclusion

This proposal, once finalized, will define the official numbering, categorization, and lifecycle rules for all Tondi Standard Proposals.

  • Before October 2025 โ†’ Sequential (TSP-000x)
  • After October 2025 โ†’ Categorized (TSP-Cxxx, TSP-Nxxx, TSP-Axxx, TSP-Lxxx, TSP-Pxxx, TSP-Sxxx, TSP-Ixxx)

This ensures clarity, consistency, and scalability for the long-term evolution of the Tondi ecosystem.