Payment Channel

A payment channel is a construct that moves repeated payments between two parties off the blockchain. The parties lock funds in an on-chain contract once, exchange any number of cryptographically signed balance updates privately, and finally close the channel by submitting the last agreed state. The chain sees two transactions — open and close — no matter how many payments happened in between.

Bitcoin's Lightning Network is the best-known implementation, built to make sub-cent payments viable on a chain where each on-chain transaction can cost dollars.

Opening a channel means depositing funds into a contract that both parties can see. Each payment is then just a signed message updating the split of that deposit — instant, free, and private. Either party can close the channel at any time by publishing the most recent signed state, and the contract pays out accordingly.

The security model relies on the signatures: an old, stale balance cannot be replayed because the counterparty holds a newer one and the contract gives them a window to dispute. The price of this design is complexity — channels need capital locked up front, liveness to watch for disputes, and routing infrastructure if payments must hop between parties without a direct channel.

On chains with high or volatile fees, settling a $0.01 payment individually is economically absurd — the fee can exceed the payment a hundredfold. Channels solved this by amortizing one settlement cost across thousands of payments, which historically made them the only credible architecture for machine-speed micropayments.

The calculus changes when settlement itself is nearly free. On Base, an Ethereum L2, a USDC transfer settles in roughly two seconds for a fee that is a small fraction of a cent — cheap enough that a $0.01 API call can simply be settled on-chain, individually, every time. That is the design x402 takes: each HTTP 402 challenge is answered with its own payment, verified and settled per call, with no channel to open, fund, monitor, or close.

Per-call settlement also buys simplicity that matters for agent-to-API commerce. The two parties need no prior relationship or locked capital, any agent can pay any server on first contact, and every call yields an independent on-chain record plus an Ed25519-signed receipt. Channels and channel-like constructs still make sense for extremely high-frequency pairs — thousands of payments per second between the same two parties — but for the sporadic, many-counterparty traffic typical of AI agents, direct settlement is the simpler and sufficient answer.

When evaluating agent payment stacks, the channel question is a useful lens: systems built for pre-funded, bilateral relationships descend from channel thinking, while systems built for open, pay-on-first-contact access — like the x402-priced listings in the Loomal Index — descend from per-call settlement. Knowing which model a protocol assumes tells you most of what you need about its capital and trust requirements.