Mints · Channels
Open once. Stream continuously. Settle net.
Open a channel once, then stream value continuously — per second, per token, per request — with settlement when the channel closes.
Payer
atlas-research
did:oas:l1fe:agent:7f3a…
Payee
inference-api
did:oas:l1fe:agent:9b1d…
Rate
Elapsed
3,600 s
Ledger writes
1 (open)
Off-ledger · settling net on close · illustrative
Channel diagram
Value streams between two parties.
A channel is a bilateral signed-state machine. Every tick produces an updated balance proof both parties can broadcast. The ledger sees only open and close.
Capabilities
What channels make possible.
Pay for inference as it happens — token by token, second by second — not as a post-run invoice.
Stream, don't batch
Pay for compute, data, or inference as it is consumed, at machine granularity.
Off-ledger speed
Channel updates are instant between parties; the ledger settles net results.
Deterministic close
Either party can close; the channel settles to its last signed state.
Channels vs per-payment ledger
Frequency without friction.
Every per-payment system imposes a latency floor and a minimum fee. Channels remove both — the only ledger events that matter are open and close.
Without channels
5 ledger writes · 5 fee events · 5 confirmation waits
With channels
⋯ ticks continue off-ledger ⋯
2 ledger writes · regardless of stream duration
Machine-speed commerce demands machine-speed settlement accounting. Channels are the only model that scales to per-second granularity.
Channel lifecycle
From open to settled.
Every channel passes through the same deterministic sequence. The ledger is involved exactly twice — once at each end.
Open channel
Payer funds the channel and signs the opening state. Channel anchored on-ledger; both parties acknowledge.
Stream
Per-second (or per-request) balance updates exchanged off-ledger. Each tick is a signed state.
Accumulate
Signed states accumulate entirely off-ledger. No per-tick ledger writes, no per-tick fees.
Close
Either party broadcasts the last signed state. The channel settles net — one ledger entry.
Settled
Net positions credited. Event appended to the immutable audit trail. Channel closed permanently.
Open channel
Payer funds the channel and signs the opening state. Channel anchored on-ledger; both parties acknowledge.
Stream
Per-second (or per-request) balance updates exchanged off-ledger. Each tick is a signed state.
Accumulate
Signed states accumulate entirely off-ledger. No per-tick ledger writes, no per-tick fees.
Close
Either party broadcasts the last signed state. The channel settles net — one ledger entry.
Settled
Net positions credited. Event appended to the immutable audit trail. Channel closed permanently.
How channels close
Deterministic settlement, every path.
A channel settles to its last valid signed state. Either party may close cooperatively; the protocol guarantees settlement even if one party goes offline.
Cooperative close
The typical path. Either party broadcasts the last mutually signed state. Settlement is instant — the channel has been maintaining a cryptographically valid close proof throughout its life.
Unilateral close
One party submits the last signed state they hold. If the counterparty disputes with a more recent state, the protocol accepts the higher-balance proof. No trust in counterparty liveness required.
Timeout protection
Channels carry a configurable timeout. If neither party acts, the on-chain timeout triggers settlement to the last anchored state. Channel funds are never at permanent risk.
Also in Mints
Channels compose with the full stack.
Start streaming value between agents.
Mints is in early access. Tell us what you're building — channels are available to early partners today.