Batch open & close

Atomic batch is an engine capability of every core: open multiple streams in one all-or-nothing call, and revoke a set of streams in one call (each settles first; a journal re-drives the close after a crash until every member is revoked). On the escrow rail (contract version 1) a batch open is ONE on-chain transaction through the sealed vault entrypoint openStreamsBatch; on control and card it is journaled with full rollback. A partial failure leaves zero orphan allowances.

Wire availability

The wire client (@dynamoprotocol/sdk 4.3.3) does not expose a batch() call, and the owner API (1.8.0) has no batch route. Batch (and subscribe) are capabilities of the engine library inside the core, not something a client can call in this release. This page documents the engine's semantics.

Until then: open streams sequentially and treat the budget's Σ inequality as your safety net - the engine refuses any open that would break the funded ceiling, so a partial fan-out can always be revoked cleanly.

Atomicity is the contract

If any stream in a batch cannot open - a cap that would break the budget's Σ inequality, an invalid service node, a backend refusal - the WHOLE batch fails and no live stream remains afterwards: every stream the batch opened is revoked (on the escrow rail the single transaction never opens any). There is no partial success to clean up, on any rail.

Two notes carried from the engine surface:

per-stream verified-engine material; dialed streams open individually. Passing it inside a batch fails closed rather than dropping the dial.

rate, an optional SLA terms hash and meta. A category or mandate in an entry is refused, and so is a batch under a budget mandate that names its categories; open those streams one by one.