// A messaging protocol connecting developers to subnets.

Empowering Subnets to Monetize On-Chain AI Inference and Capture Every Per-Call Fee

With just a few lines of code, Web3 builders can experience the power of Bittensor through Telegraph — a permissionless, cross-chain protocol that enables access to external blockchains from smart contracts.

Developers use Telegraph to build AI-powered, cross-chain applications

By integrating Telegraph into their smart contracts, developers can make secure, verifiable API calls via the Telegraph's Port contract to any subnet. These calls enable developers to build AI-enhanced, cross-chain DeFi, NFT, and data-driven applications into their existing projects while allowing subnets to monetize their AI inference and data services through API calls. Eventually, developers can pay subnets in $TAO for each API call, helping subnets generate revenue.

Node runners on the Telegraph protocol

Node runners purchase nodes with $TAO and receive $wTAO by supporting every API call initiated by dApps to subnets. Each successful message or inference request triggers token rewards, creating a sustainable supply of wTAO for node operators while securing the Telegraph protocol.

The Bittensor ecosystem flourishes

The Bittensor ecosystem thrives by enabling developers, node runners, and subnets to collaborate in building smarter, interoperable applications. $TAO serves as both the currency of value and the bridge connecting subnets to the world beyond Bittensor, fueling innovation and growth across the network.

// Truly Open Protocol

How Telegraph Works

Imagine every time a user or app sends a cross-chain instruction — like moving USDC from Base to BNB — the protocol detects this event, validates it on-chain, and then submits it to the destination chain.

// Truly Open Protocol

The Protocol That Lives On-Chain

Permissionless

Fast & Dynamic Routing

Without Central Authority

Ready for Integration

Unlike traditional systems that rely on off-chain services or centralized middleware, Telegraph’s protocol is fully embedded in the on-chain logic. It constantly observes activity across supported blockchains and responds dynamically, ensuring seamless and real-time cross-chain interactions.
Because it’s permissionless by design, there’s no need to register, trust a third party, or rely on wrapped assets. Instead, developers gain access to a native relay layer that any dApp can plug into. Each node within the network becomes an active agent of the protocol.
By removing gatekeepers and placing intelligence directly within the protocol, Telegraph empowers developers to build truly interoperable applications — fast, trustless, and open to all.

1. Detect

Nodes constantly monitor the blockchain for cross-chain message requests. They act as watchers, listening for events across supported chains in real time.

2. Validate

Once a message is detected, nodes verify its data and integrity using deterministic validation. No central approval—just open, mathematical consensus.

3. Submit

The selected node (based on round-robin) submits the verified message to the destination chain. No racing, no MEV, just orderly propagation.

4. Earn

In return for their role, node runners receive wTAO rewards. More uptime and reliability equals more consistent earnings.

Truly Open Protocol

Fee Structure & Rewards

// Telegraph On-Chain

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.

// Telegraph API

Credits can be purchased via credit card based on API usage. The API provides access to all subnets integrated with Telegraph.

Token Distribution (Round Robin)

20 Nodes after 100,000 Transactions (250 Tokens Total)
Total Tokens Earned


(2.5 wTAO per node)

250 wTAO

Node Schedule & Price

View node timing and pricing on Telegraph.
Nodes Secured

1/99

Use Cases for Telegraph and Subnets

Building a Stronger Subnet Through Growth & Participation

Each message strengthens the network by attracting more validators, increasing liquidity, and reinforcing the cycle of decentralized growth.

1. Validation Demand

More cross-chain activity increases the need for message verification.

2. More Node Runners Join

Higher rewards attract new node operators to meet the demand.

3. Liquidity Grows

Transaction fees are routed to pools, deepening available liquidity.

4. Ecosystem Strengthens

A larger, more active network creates stronger security and coverage.

Ahmed Ali - Lead Protocol Engineer

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.

// Telegraph is open to you.

Get Started

Start building in minutes. Simple steps to launch your project smoothly.

Run your own node. No signup needed — earn rewards, support the network.

Join the network today. Build, connect, and grow with a global community.

Learn more title

Lorem ipsum dolor sit amet, consectetur adipiscing

“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

“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

RoadMap

Phase Time Period Goal Key Deliverables Roles
Libp2p & Communication Consensus September – October 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 October 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
Merkle Proof & Verification Layer December 2025 – January 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 January 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
P2P Networking & Consensus MVP January – February 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 engine
  • Fault-tolerance testing
  • Deliver MVP by Feb 2026
Protocol: Networking + consensus
DevOps: Stress testing
Explorer APIs & Dashboard February – March 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 network
  • Documentation + onboarding for devs
  • Stable production launch
Security: Audit
Protocol: Final consensus
DevOps: Onboarding