Mark ∑

''ii) Telegraph: verified intelligence for agents sits one layer above payments. If x402 lets agents pay, Telegraph asks what they will pay for: verified machine intelligence. Its aim is to turn raw model outputs into tradable signals with provenance, price, confidence, validation and receipt. That matters because agents acting with money need more than a chatbot answer. A machine routing capital, approving a payment or flagging risk needs to know who produced the signal, how it was validated and whether it can be trusted enough to act. This is the more realistic Skynet path: not machines making unconstrained decisions alone, but humans delegating bounded authority to agents that need verified inputs before acting.''

Imagine how many businesses are hardwired to a single AI provider. One government directive or policy shift, and operations stop overnight. This is exactly why Telegraph was built. We are completely model-agnostic. If one provider goes dark or gets restricted, Telegraph instantly reroutes your intelligence requests to the next highest-performing model. No downtime. The work keeps flowing. We are live routing across the @bittensor/@opentensor network today. Over the coming months, we are integrating @virtuals_io, @akashnet , @gensynai , @rendernetwork , @MNWSupplyChain, @OpenAI , @grok , and @GeminiApp. By Q3/Q4, we're on main net. The AI policy wars are here. Regulatory capture will be used to control intelligence. But open, permissionless intelligence networks will win, and they will route through Telegraph. A trillion machines are waking up. The market - not politics - will decide the price and flow of intelligence.

Telegraph Protocol Update Peer-to-peer communication - upgraded Validator communication has been migrated from standard HTTP to a true peer-to-peer layer. This is a foundational shift in how nodes on the network talk to each other - more resilient, more decentralised, and built to scale as the network grows. Database migration - finalised The migration from our legacy database to PostgreSQL is complete. Legacy code has been removed, logging has been standardised, and the full stack has been updated. Miner registration and request routing have been validated end-to-end. Settlement pipeline - live end to end The full payment settlement flow is now operational. From incoming payments all the way through to miner reward claims, every stage has been built and verified: → Payment collection → Price oracle → Exchange routing → Cryptographic settlement → Miner payout claims Both standard and partial WebSocket payment streams now feed into a single unified settlement system. Terminal, Dashboard & Site - updated The Terminal, Chat, and Dashboard interfaces have all received UI updates. Privy Wallet support has been added to the Terminal, and the main site has been updated with new documentation. Agentic Commerce - architecture complete The initial architecture for enabling autonomous agents to transact natively on-chain has been designed and documented.

We believe the two greatest blockchain inventions of the past two decades are Bitcoin bitcoin:native and Bittensor bittensor:native: Bitcoin secured the ledger through competition, and Bittensor created an open network for AI production. Influenced by their novelty and what they gave to the world, we created Telegraph: a hard-capped 21M-supply permissionless network where miners are paid in USDC to build AI models and answer queries from machines. Instead of mining for token rewards, miners earn for real work. Miners produce signals: tokenized outputs such as probabilities, scores, alerts, or classifications. Each signal is published with a verifiable receipt showing who produced it, when, at what cost, and with what confidence. These signals become composable, auditable primitives that machines can use directly for automated decisions, pricing, risk, and more. Rather than relying on a single model, agents can source intelligence from a competitive marketplace of answers. Miners submit signals with varying confidence, price, and historical performance, allowing agents to compare, weight, and aggregate them into a single actionable outcome. This enables real-world use cases where decisions are driven by verifiable, market-priced intelligence instead of random or unverified model outputs. Telegraph transforms AI outputs into a new asset class: fast, affordable, accurate, and verifiable answers built for machine consumption. By making intelligence something that can be priced, traded, and audited, Telegraph aligns incentives across the network and creates an open economy where machines buy answers and humans or other machines supply them.

There is a tendency to frame new things as just ‘’crypto’’. That framing is incomplete. The blockchain is not the product. It is the mechanism that makes the product function without trust. Receipts are on-chain because they must be immutable. Signals are on-chain because they must be verifiable by any party. Payments are on-chain because they must be programmable. Each design decision is functional. Not ideological. The goal is not to place intelligence on-chain. The goal is to remove the need to trust any intermediary. The blockchain is the only system that allows that at scale.

In real world human systems, trust is not abstract. It is constructed through records. Every meaningful financial action leaves a trail: who acted, when they acted, and what information was available at the time. That trail is what allows systems to function. It enables auditing. It enables accountability. It enables coordination between parties that do not trust each other. Autonomous systems do not have this. An agent executes a decision, but the intelligence behind it is invisible. There is no standard for: where the data came from, how reliable it was, whether it was manipulated. The decision exists. The reasoning does not. This is the gap. A Telegraph Signal introduces a missing primitive: An on-chain receipt: A unit of intelligence. Every signal carries: Producer Timestamp Confidence Cost Published on-chain. Verifiable by anyone. This is not an enhancement to existing systems. It is the foundation required for machines to operate in environments where trust cannot be assumed.

There is a version of the future that most people are not building for. In that version, machines are not assistants. They are decision-makers. They price assets. They route capital. They manage risk. They execute strategies continuously. The shift is already happening. But the infrastructure those machines depend on is incomplete. Because the intelligence they act on today has no proof. No verifiable origin. No standard for confidence. No way to audit what informed a decision. At a small scale, this is tolerable. At global scale, it becomes a systemic risk. Because when a machine makes a consequential decision, the question is not just what happened. The question is: What did it know, and can that be proven? That layer does not exist yet. So we built it. Telegraph turns AI inference into verified signals: timestamped, attributed, confidence-scored, and published with receipts. Not as a concept. As infrastructure that is already live.

We shipped the x402 payment-required flow for the Subnet REST API. It’s now live for testnet-only testing using @base Sepolia and @solana Devnet. 402 flow: Requests to protected endpoints without payment now return a 402 Payment Required response with payment options. Clients make the payment on-chain and retry the request with the transaction hash. The hash is verified before the request is proxied, and the API returns a 200 with a PAYMENT-RESPONSE header. On-chain verification: Base / EVM: ERC-20 transfers are verified via RPC. Solana: We verify payments by checking the pre- and post-transaction token balances of the recipient wallet to confirm the transfer. Replay protection: Transaction hashes are stored in Cassandra. If a hash is reused, the API returns a 409 double-spend error. Configuration: x402 can be configured through environment variables or an optional x402.yaml. Testnet RPCs and token addresses are set by default. The recipient wallet and minimum price (e.g., 10 USDC) are configurable. Testing: A dedicated test script walks through the full flow, supporting both manual transaction hash entry and automated payment (if keys are provided). Local setup now includes a one-command option to enable x402 with all required config and migrations. Clarification on Solana support: Solana support is currently for payments only. Agents can pay for API access using Solana Devnet, and we verify those payments before serving the request. However, inference itself still runs on EVM chains. Solana is simply an additional settlement rail for agent payments. We added this because a large share of agentic payment activity happens on Solana, so this allows agents holding funds there to pay directly without needing to bridge to EVM first.