Powered by Bittensor
Telegraph is a permissionless messaging protocol that turns inference from Bittensor subnets into a verifiable, tradable on-chain commodity—the next asset class for DeFi. With Telegraph’s Port contracts—and just a few lines of code—anyone can request a signal and receive a signed answer across supported chains. We publish intelligence—answers, scores, alerts, routes, and prices—to the ledger so any wallet, DEX, CEX, trading desk, or app can let users buy, sell, swap, hedge, lend, and build with it.
A subnet’s miners compete on one job.
Outputs include risk scores, best trade routes, fair prices, depeg/volatility alerts, wallet summaries, and media authenticity checks.
Telegraph packages each result into a tiny on-chain receipt: who made it, how fast, confidence, and price.
Because it’s on-chain and verifiable, apps and markets can trust it and use it immediately.
Trustworthy: Every message is signed and checked on-chain; it can’t be faked or reused.
Plug-and-play: Any app can read and act on the same on-chain fact—no screenshots or private emails.
Tradable: The signal (and the capacity to get more) can be bought, sold, hedged, insured, or financed—like any commodity.
Everywhere: The same message can be posted to multiple chains, so people can act where their funds already are.
Answer: the result itself—risk score, route, fair price, volatility estimate, reputation tag, alert, or summary.
Price of Inference: the going price for one standard answer (our on-chain AI Price Index).
Receipt / SLA: proof of service—who served it, speed, price paid, pass/fail—for refunds and insurance.
Performance / Heartbeat: miner/subnet health snapshots for lending, routing, and reputation.
// Truly Open Protocol
Truly Open Protocol
A fee in wTAO will be charged for each cross-chain message and AI inference performed on-chain. This fee will be split 50/50 between Telegraph nodes and the Telegraph treasury.
Credits can be purchased via credit card based on API usage. The API provides access to all subnets integrated with Telegraph.
Most projects sell a token and keep the real answers off-chain. Telegraph flips it: the answers themselves are the product—public, portable, priced, and programmable—so wallets, DEXs, CEXs, trading desks, and apps can buy them, trade them, insure them, and build with them. We commoditize AI signals by standardizing the unit (“one answer” with a set quality level), attaching a receipt, publishing a public price index, and posting the same signed message across chains.
Stop building with stale data. A Telegraph Port is your single on-chain pathway to the entire Bittensor network. Integrate live signals—risk scores, asset prices, DeFi predictions, and generative AI—directly into your smart contracts. If you can build a dApp, you can build with live intelligence.
Gain an edge. Don’t just trade tokens—trade the signals that move them. Go long on risk scores or short volatility forecasts. Telegraph turns raw inference into a tradable asset class—your first-mover chance to capture alpha before it hits the headlines.
Your next asset class. Integrate Telegraph Ports to list and trade AI signals programmatically. Offer users automated risk management, create inference-based derivatives, and tap a steady flow of buy pressure from the next wave of DeFi.
Don’t let your alpha fade. Telegraph distributes and monetizes your signals across every major chain—driving durable buy pressure for your alpha token. Your sales channel to the world.
More cross-chain activity increases the need for message verification.
Higher rewards attract new node operators to meet the demand.
Transaction fees are routed to pools, deepening available liquidity.
A larger, more active network creates stronger security and coverage.
Ahmed is a lead protocol engineer who has built blockchain infrastructure from scratch for the past four years. He’s the lead engineer behind Telegraph, where he developed the cross-chain communication protocol that enables AI inference across blockchain networks, integrating Bittensor subnets within Telegraph. At RYT Chain, Ahmed designed a novel Proof of Majority consensus and reduced transaction latencies from 3 seconds to 75 microseconds. He built L2 infrastructure by forking the Optimism stack for Epic Chain. Ahmed is a Certified Blockchain Architect with deep expertise in distributed systems and a proven track record of scaling blockchain networks for production.
Join the network today. Build, connect, and grow with a global community.
“Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum
| 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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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: Audit Protocol: Final consensus Docs: Onboarding |