Settlement cycles were built around people. A batch runs overnight, balances are struck, fees are applied, and the next day begins. That rhythm works when transactions are entered by humans during working hours. It breaks when the transacting party is software that pays continuously — thousands of small operations, around the clock, each too small to justify the cost and delay a human-scale cycle assumes. The machine-speed ledger problem is what happens when the cadence of the money outruns the cadence of the system.

Why batch cycles break

A daily cycle imposes two costs on machine payments. The first is time: value that arrives tomorrow is not available to an agent that needs to act now. The second is fees: a per-transaction charge designed for human-scale payments turns a stream of small machine payments into an unviable one. Neither problem is about the protocol the agent uses; both are about the layer beneath it.

What machine-speed needs

A ledger that serves agents tends to require:

  • netting of offsetting flows, so that participants' claims cancel internally before anything leaves;
  • instant internal settlement between participants, rather than a nightly net;
  • internal FX, so conversions do not require an external hop;
  • a double-entry ledger that keeps attribution intact at speed.

The point of netting is scale. If bank A sends a large amount and recipients B and C are owed slightly less, only the difference actually leaves the hub — the rest cancels.

Keeping evidence at speed

Speed must not cost traceability. A ledger built for agents records each operation against its principal, agent and policy version, so a constant stream is still fully reconstructable. Machine-speed settlement and an auditable record are not opposites; they are two requirements of the same design.

In short

  • Daily cycles and human-scale fees do not fit continuous machine payments.
  • Netting, instant internal settlement and internal FX change the economics.
  • Offset flows cancel internally; only the remainder exits.
  • Traceability is preserved at speed, not traded away.

Explore the ledger design in the developer documentation.