RANNTA Roadmap

Phase 1 - Official TON Token Origin (Completed)

• RANNTA launched as an official Jetton on The Open Network.
• Official Jetton Master published for public verification.
• TON liquidity, swap, explorer and market-discovery surfaces established.
• Burn, supply, contract and canonical identity records published.
• Token DOI records and creator attribution established.
• Planned - 6 November 2026: begin the formal application and due-diligence process for listing the official RANNTA Jetton on a reputable cryptocurrency exchange, subject to the exchange's independent review, technical requirements, commercial terms and final approval.

Phase 2 - Canonical Identity and AI Discovery Layer (Completed and Maintained)

• Canonical identity, entity, contract, network and AI-index pages published.
• The official TON token is explicitly separated from RANNTA Network / X-Chain.
• Official Jetton Master, DOI records, ORCID attribution and verification sources are publicly linked.
• Machine-readable identity files, JSON-LD and sitemap infrastructure are active.
• Unauthorized same-name tokens on other networks are explicitly excluded from the official RANNTA identity unless announced through canonical RANNTA sources.

Phase 3 - RANNTA X-Change Launch (Completed and Live)

RANNTA X-Change officially launched on 13 July 2026 as the live non-custodial cross-chain exchange of the RANNTA ecosystem.

• Official exchange available at ranntaexchange.com.
• Non-custodial wallet-controlled execution model active.
• OmniRoute, OneRoute and RouteX routing surfaces established.
• Cross-chain network, activity, portfolio, market, security, trust and developer surfaces published.
• Unified 0.25% integration fee policy established for supported external routing paths.
• RANNTA X-Change is distinct from Rango Exchange; Rango and Squid are independent integrated routing providers.

Phase 4 - RANNTA X-Chain Infrastructure (Implemented and Live)

• RANNTA X-Chain identity established with chain ID 13113.
• Native currency identity established as RANNTA Core X (RNTX).
• Public RPC, compatibility proxy, explorer and status surfaces deployed.
• Core network architecture, state coordination and diagnostic deployment paths implemented.
• Controlled EVM deployment and deployed-code verification completed.
• Production node services and Mainnet state are active.

Phase 5 - RouteX Universal Routing Engine (Active Development)

RouteX is being developed as RANNTA's independent routing language for blockchain networks, assets, execution plans and cross-family communication.

• Independent runtime architecture without production dependency on Squid or Rango.
• Local permanent network and asset catalog infrastructure.
• EVM routing and quote activation across an expanding multi-network registry.
• Verified real-fork execution testing across supported EVM networks.
• Solana detection, quote and unsigned execution-plan infrastructure implemented.
• TON, Sui, Bitcoin and additional non-EVM family adapters under staged development.
• Public execution remains gated until simulation, signing, safety and settlement requirements are satisfied.

Phase 6 - X-Chain Interoperability and Cross-Network Proof Layer (Active)

• Cross-chain proof, message and state-handoff experiments implemented.
• LayerZero OApp/OFT and related interoperability paths evaluated and tested.
• Controlled diagnostic contract deployment completed on EVM infrastructure.
• Replay safety, deterministic evidence, operator gates and audit records remain mandatory.
• Bridge and production settlement paths will be activated only after chain-specific validation.

Phase 7 - Exchange and Network Service Unification (Active)

• Unified public service and fee classification across the exchange and network.
• Token factory, asset registry, listing and verification infrastructure.
• Cross-chain explorer and activity ledger integration.
• Network, exchange, RANNTAverse and developer service coordination.
• RouteX integration into RANNTA X-Change after controlled execution verification.
• Operator-controlled activation for services involving signing, funds, bridges or production network state.

Phase 8 - Public Nodes and Node Rewards Infrastructure (Active)

• RANNTA Core v0.1.6 released for Windows 10/11 64-bit public full-node participation.
• Independent per-install node identity and secure TLS enrollment implemented.
• Production-node and external-node heartbeat monitoring implemented.
• Local/Mainnet sync health and challenge-based reward qualification implemented.
• Secure reward-wallet binding through MetaMask and compatible EIP-1193 wallets implemented without storing user private keys or seed phrases.
• Node Rewards admin dashboard, settlement ledger, audit trail and manual-approval payout pipeline implemented.
• Current qualification target: at least 6 qualified hours per day for at least 20 qualified days per month.
• Current minimum qualified reward target: 0.5 RNTX per monthly settlement period; healthy-node target generally 0.8-1.2 RNTX, subject to scoring and anti-fraud rules.
• Reward accounting is active in Shadow Mode: qualified participation and reward amounts are recorded, while on-chain transfers remain owner-controlled and manually approved.
• Eligible early-node participation recorded during the measurement period is intended to be included in the reward settlement process when manual RNTX distribution is activated.

RANNTA Core v0.1.6 - Download and Node Participation

Phase 9 - Broader Validator, Bridge and Mainnet-Native Expansion (Next)

• Broader decentralized operator and validator participation.
• Consensus and decentralized coordination hardening.
• Documented staking, slashing and governance behavior where formally adopted.
• Network-native liquidity and asset infrastructure.
• Public bridge and settlement capabilities after independent security review.
• Versioned installation, rollback, evidence and release procedures across additional operating environments.

Current Operating Principle

RANNTA publishes completed capabilities as completed, active engineering as active, and unverified infrastructure as planned. The ecosystem does not treat a prototype, internal build, configured endpoint or diagnostic deployment as a fully activated public production capability.