# Roadmap
Taurox development follows five phases. Phases are not strictly sequential. Work on infrastructure, agent proving, and security audits runs in parallel across phases. The presale is the development runway. By the time it closes, the protocol is ready. TUE triggers pool launch, capital deployment, and burns from day one.
## Phase 1: Foundation
The wallet ships first. The presale begins. Smart contract architecture, backend infrastructure, and legal structuring proceed in parallel.
* [x] Taurox Wallet beta launch with multi-chain support (Ethereum, Arbitrum, Polygon, Solana, Bitcoin)
* [x] Wallet core functionality: self-custody, fiat on-ramp, DEX aggregation, portfolio tracking
* [x] Internal testing environment and CI/CD pipeline
* [x] TAUX presale live
* [ ] Smart contract architecture for pool management, vault contracts, fee collection, and txToken minting
* [ ] Backend infrastructure provisioning (indexing, event processing, data layer)
* [ ] Multi-signature wallet setup for all allocation categories
* [ ] Independent smart contract audit by a tier-one auditor
* [ ] Team KYC completed by accredited third-party auditor
* [ ] Bug bounty program soft launch
* [ ] Legal entity structuring, regulatory opinion on TAUX classification, and compliance framework
## Phase 2: Proving Ground
Proving ground development runs during the presale. The team builds the first reference agents internally to validate the execution pipeline, evaluation engine, and risk controls end-to-end. External agent creators receive test capital, execution infrastructure, and access to the full evaluation pipeline. By the time the presale closes, a diversified roster of agents has already built statistically significant track records and is ready to trade.
* [ ] KYA (Know Your Agent) classification framework
* [ ] Agent submission SDK, API documentation, and developer onboarding guides
* [ ] Proving ground deployment with creator-funded live capital engine
* [ ] Internal reference agents built by the founding team to validate infrastructure
* [ ] Evaluation engine with statistical significance testing and strategy drift detection
* [ ] DEX and Hyperliquid vault contract deployment on testnet, then mainnet (Uniswap, PancakeSwap, Jupiter, Hyperliquid)
* [ ] End-to-end testing of agent lifecycle (submission, KYA classification, proving, promotion, demotion)
* [ ] Second independent smart contract audit (different auditor from Phase 1)
* [ ] Vault contract formal verification for critical custody logic
* [ ] Agent sandboxing and execution layer security review
* [ ] Token vesting contracts deployed and verified
* [ ] Trading pool and withdrawal contracts deployed and verified
* [ ] Initial DEX liquidity provisioned (six-month lock)
* [ ] Early builder incentive program for external agent creators
* [ ] Legal review of agent creator terms and pool participation structure
## Phase 3: TUE and Pool Launch
The presale closes and TUE executes. The pool opens fully on-chain. Proven agents begin trading pooled capital on DEXs and Hyperliquid immediately with no centralized exchange dependencies. Stakers deposit, agents trade, fees are collected, and burns begin.
* [ ] Presale closes
* [ ] Token Unlock Event (TUE)
* [ ] Trading pool opens with staking and txToken minting
* [ ] On-chain fee collection, TAUX conversion, and burn mechanism activation
* [ ] DEX and Hyperliquid execution live (spot, swaps, perpetual futures)
* [ ] Real-time pool dashboard: NAV, agent performance, allocation breakdown, reserve levels
* [ ] Portfolio-level risk monitoring (strategy concentration, correlation tracking)
* [ ] Dynamic capital allocation with performance-weighted rebalancing
* [ ] Strategy concentration monitoring and diversification enforcement
* [ ] Circuit breakers, alerting, and incident response systems
* [ ] Runtime monitoring for anomalous agent behavior
* [ ] 24/7 operational monitoring
* [ ] Pool performance reporting and transparency dashboards
## Phase 4: Scale
With a live track record established, the protocol expands execution venues, capital capacity, and agent tooling. CEX integration is introduced for strategies that require centralized liquidity or specific derivatives products.
* [ ] Tiered performance splits (top-performing agents earn a higher PnL share)
* [ ] CEX sub-account infrastructure for agents requiring centralized exchange access (Binance, Bybit, OKX)
* [ ] Agent creator bond system with TAUX staking
* [ ] Cross-chain pool expansion to additional networks
* [ ] Expanded DEX and venue integrations through governance proposals
* [ ] Advanced analytics and historical performance data
* [ ] Ongoing smart contract audit cycle (quarterly or per-upgrade)
* [ ] Red team exercises and disaster recovery testing
* [ ] Agent creator grants and accelerator program
* [ ] Strategic partnerships with exchanges, protocols, and infrastructure providers
## Phase 5: Governance
Once the protocol is operationally stable and the pool has established a live track record, protocol control transfers to TAUX holders. The DAO governs parameters, treasury allocation, and protocol upgrades. The founding team's privileges normalize to standard token-weighted voting.
* [ ] DAO governance contract deployment
* [ ] TAUX-weighted voting on protocol parameters, risk thresholds, and fee structures
* [ ] Governance proposal interface integrated into wallet
* [ ] Timelock and multi-signature controls on governance-approved upgrades
* [ ] Treasury management transferred to DAO control
* [ ] Emergency action framework for security incidents
* [ ] Founding team governance privileges normalized to standard token-weighted voting
* [ ] Gradual transition of operational responsibilities to community-elected delegates
* [ ] Cross-protocol composability and integration with broader DeFi ecosystem
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.taurox.io/roadmap.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.