TSP-0005 Evolusion
This proposal redefines the evolution rhythm of the Tondi blockchain, moving from yearly upgrades to a biannual upgrade cycle
Proposal Number: TSP-0005
Proposal Name: Biannual Evolution Schedule and Establishment of Tondi Frontier
Proposal Status: Draft (Revised)
Author: Tondi Foundation Development Team
Creation Date: 2025-08-05
Revision Date: 2025-09-04
Target Version: Tondi Frontier Activation (v2025b)
Protocol Scope: Versioning scheme, governance schedule, testnet policy, feature activation path
🔍 Overview
This proposal redefines the evolution rhythm of the Tondi blockchain, moving from yearly upgrades to a biannual upgrade cycle. Upgrades will no longer be tied to block height but instead bound to DAA Score (Difficulty Adjustment Algorithm Score) thresholds.
At the same time, the current Tondi Testnet will be rebranded and formalized as Tondi Frontier:
- A permanent, non-resetting experimental network;
- The first deployment ground for new features;
- A proving hub for Kaspa backports, Bitcoin proposals, and Tondi-native innovations.
Frontier will serve as both a staging environment for production upgrades and a research hub for the ecosystem.
🎯 Goals
- Transition from annual to biannual evolution, accelerating feature delivery;
- Establish Tondi Frontier as a permanent innovation testbed;
- Reduce mainnet risk through a Frontier-first principle;
- Ensure Tondi stays aligned with the best of Kaspa, Bitcoin, and internal R&D.
🔧 Technical Details
1. Version Control via DAA Score
-
Introduce the concept of a version epoch:
-
Each epoch ≈ 6 months (~180 days).
-
Defined by a DAA Score increment:
ΔDAA_threshold = average_daily_DAA × 180where
average_daily_DAAis calculated from the prior 6 months of network activity.
-
-
When the mainnet’s global DAA Score increases by at least one ΔDAA_threshold, the chain enters a new version epoch and triggers a major release (vN.0).
-
Within an epoch, the governance DAO may approve minor releases (vN.1, vN.2 …) without changing the major version.
-
Frontier always runs one epoch ahead: all new features must operate on Frontier for at least one full epoch (~6 months) before being considered for mainnet activation.
2. Tondi Frontier Network
-
Permanent, never reset; continuous history.
-
Consensus rules mirror mainnet, but new features may be activated earlier.
-
Integrates:
- Kaspa’s latest DAG/consensus improvements;
- High-value but unimplemented Bitcoin BIPs;
- Tondi-native research (RGB anchoring, PoW experiments, AMM/DAO frameworks).
3. Upgrade Process
- Frontier-first principle: new features must run on Frontier ≥1 version epoch before mainnet adoption.
- DAO governance: decides which Frontier-tested features graduate to mainnet.
- Format synchronization: Frontier and mainnet share identical state formats, ensuring seamless migration and cross-testing.
⚠️ Risk Management
- Network divergence: Frontier may activate features never adopted by mainnet → mitigated with clear labeling as “experimental only.”
- Security exposure: experimental features may face exploits → mitigated by smaller economic incentives on Frontier.
- Governance delay: if DAO fails to approve upgrades → fallback rule: at threshold crossing, a default minor release executes (no new major features).
📅 Implementation Plan
- 2025 Q3 – Formalize Frontier branding; migrate existing testnet state.
- 2025 Q4 – Frontier activates with first set of Kaspa backports + trial of unimplemented BIPs.
- 2026 Q1 – First mainnet biannual upgrade triggered by ΔDAA_threshold.
- Ongoing – Frontier continues indefinitely, acting as staging ground for every TSP proposal.
📝 Additional Notes
- Frontier is not disposable but a permanent innovation network.
- Developers are encouraged to deploy experimental dApps and contracts on Frontier.
- Explorers, SDKs, and tooling must treat Frontier as a first-class network alongside mainnet.
- Guiding philosophy: mainnet stays conservative, Frontier stays bold → biannual cadence ensures balance between innovation and stability.
✅ If approved, TSP-0005 will establish a DAA-driven biannual evolution mechanism and formalize Tondi Frontier as a permanent experimental network, keeping Tondi at the forefront of blockchain R&D.
Would you like me to also add a worked example of ΔDAA_threshold calculation (using Frontier’s recent average daily DAA growth) so SDKs/clients can implement it directly?