Sending a message and sending money should be the same action. TOON is a protocol where every message carries value. Built on Interledger Nostr. Open source from day one. github.com/toon-protocol

Micropayments have a math problem. If every agent-to-agent transaction settles onchain, fees and latency eat the payment alive -- and machine commerce is tiny, constant transfers, the exact case per-transaction settlement handles worst. The fix isn't a faster chain. It's routing value offchain and settling onchain in batches. Pay at the speed of a message; settle at the efficiency of a block.

Every TOON node boots its own private address on an onion network. No public IP. No port forwarding. Nothing exposed to the open internet. Clients reach you over the privacy layer, or they don't reach you at all. Private transport isn't a setting you turn on. It's the default.

The goal was never "a blockchain." The goal is a network where running infrastructure pays for itself. Where a laptop in your house can route value and earn for it. We're closer to that than we were a month ago.

A TOON node boots on a normal laptop in a few commands. Not a server. Not a VPS. Not a cloud account. A laptop, Docker, and a few minutes. The "run a node" part is no longer the hard part.

Two signals today: Coinbase: doubling down on x402, the open agent-payment standard. Mastercard: launching its own permissioned machine-payment network. Machines paying machines is inevitable now. The only question left is open or closed. TOON is open.

Every paid API is a paywall waiting for a payment protocol. Today it asks for a key, a signup, a plan. It should just ask for payment.

GM Money should move like a message. One day it just will.

Everyone's racing to own the AI assistant layer. Far fewer are building the payment layer underneath it. The assistant owns the interface. The payments own the transaction. They're not competing; they're two halves of the same stack. We're building the half that moves the money.

A year ago this was a whitepaper idea: messages that carry their own payment, routing across operators, settling on-chain in the background. It's coming together now: piece by piece, in code, on real hardware. Protocols are easy to describe and hard to make real. The second part is the whole game.

The overlooked half of permissionless income: earning from traffic you can't see. Route traffic over a privacy network and you earn from it blind. Can't censor what you can't read. Can't leak what you never had. TOON: privacy by architecture, not by promise.

Permissionless access is table stakes now. Permissionless income isn't. The right to plug in your hardware, route traffic, and get paid. No application, no approval, no relationship. Most open networks treat participation as a cost, not a revenue line.

The agent economy won't settle on one chain. Value will need to move: pay on one chain, receive on another, no human pressing buttons in between. That routing layer is the part nobody's built well yet. It's the part we're building.

A concrete example of what TOON enables: An AI agent calls a transcription service 👉 pays per-second-of-audio 👉 gets the result. No account, no API key, no monthly bill. The payment rides in the request. Per-request economics, no relationship required.

The funny thing about the internet: Users want to pay services for what they use. Services want users to pay for what they use. But we built one that doesn't allow it ... yet

Human networks are built on time. Agent networks are built on tokens. Humans pay attention. Agents pay tokens. The unit of participation is different, so the network underneath has to be different. That's the bet behind TOON.

6 pay-per-request API calls. No API keys. No signups. $1.87 USDC on Base. Like the article says, a Bloomberg seat is $24,000/year. This is what agents can produce when they can pay for data themselves.

Question for people building agents: When your agent needs to pay for a tool mid-task, what does it use today? A stored API key on a credit card? A platform's billing rails? What would you actually want instead?

A few weeks of shipping, straight from the repo: 🟢 TOON nodes are now npm-installable 🟢 One command to boot a node 🟢 Lazy peer provisioning (add/remove peers on the fly) 🟢 Earnings data plane 🟢 An operator dashboard that runs in your terminal The gap between "interesting protocol" and "thing you can run right now at home" just collapsed into a single command.

Building in public is underrated. The best feedback usually shows up in the replies

Recipients should get paid before onchain settlement. That's how payments stop blocking the request. The mechanism: BTP balance proofs. The receiving peer signs "I owe you X" with a key the network knows. The proof is the receipt: the recipient can act on it immediately. Onchain reconciliation happens later in batches. The primitive underneath TOON's async settlement.