Telegraph

Phase	Time Period	Goal	Key Deliverables	Roles
Libp2p & Communication Consensus	September – December 2025	Developers will be able to run nodes that talk to each other directly (P2P) instead of relying on a single server. This makes the system faster, more reliable, and cheaper to scale.	Replace HTTP with libp2p Implement node-to-node consensus for consistent results Remove single-node dependency Validate under multi-node load	Protocol: libp2p, consensus Back-end: Node sync DevOps: Distributed testing
Replay + Reprocess	September – December 2025	Any developer request can be replayed deterministically, meaning retries always give the same result. This ensures dApps don’t break and saves time/cost when handling failed transactions.	Replay/reprocess mechanism Deterministic result verification Metrics + logging	Back-end: Replay logic QA: Determinism testing
Subnet Integration (Initial Batch)	October – December 2025	Developers will be able to access 20+ priority subnets and call their inference functions cross-chain. This unlocks new products with real AI utility directly on-chain.	Integrate Subnets (1, 10, 11, 18, 19, 20, 22, 32, 33, 34, 39, 41, 42, 44, 54, 57, 63, 64) Register subnet IDs for inference requests Enable wTAO payments for inference Deploy first on-chain transactions by 15 Dec 2025	Smart Contracts: Subnet + wTAO integration Back-end: API payments DevOps: Testnet
P2P Networking & Consensus MVP	January – March 2026	Developers will benefit from a stable peer-to-peer network where data is always synchronized and consistent. This reduces downtime and enables reliable cross-chain messaging.	P2P networking module Lightweight consensus Fault-tolerance testing Deliver MVP by Feb 2026	Protocol: Networking + consensus DevOps: Stress testing
Merkle Proof & Verification Layer	March – April 2026	Developers will get trustless validation of cross-chain messages. Every message will be provable via Merkle proofs, lowering risk of fraud and making the protocol enterprise-ready.	Merkle tree construction Merkle proof + bitmap verification Contract upgrade for proof validation Integrate replay with Merkle verification	Cryptography: Merkle Smart Contracts: Verification
Validator Node Governance	May – June 2026	Companies and independent operators will be able to join the validator network, pay fees, and participate in governance. This ensures decentralization, fairness, and higher trust.	Node subscription process (public key + fee) Governance contract for node faults Byzantine fault detection Threshold approval for messages	Protocol: Node governance Smart Contracts: Governance Security: Monitoring
Explorer APIs & Dashboard	March – August 2026	Developers and enterprises will have an explorer + dashboard to track messages, subnet usage, credits, and payments. This reduces integration time and helps teams monitor their apps.	REST APIs for explorer Dashboard with transaction + subnet metrics Credit/payment monitoring	Back-end: APIs Front-end: Dashboard UI DevOps: Deployment
Expanded Subnet Rollout & Scaling	March – August 2026	Developers will be able to access more subnets at scale, with cheaper API costs and higher throughput. Companies can build multi-subnet applications without reliability issues.	Add more subnets Optimize credit/payment API Multi-subnet stress tests Full P2P + consensus rollout Public explorer launch	Smart Contracts: Subnet integration Back-end: Scaling Front-end: Explorer QA: Load testing
Production Release	August – September 2026	Telegraph becomes production-ready, meaning developers and companies can confidently use it for cross-chain + AI applications at scale.	Security audits of Ports, Merkle proofs, and governance Load testing under full usage Documentation + onboarding for devs Stable production launch	Security: Audit Protocol: Final consensus Docs: Onboarding

Telegraph Marketplace

Learn more title

RoadMap