Changes to “One transaction per account per block, and batches”
#850 (zoobc.how, 2026-10-26 22:31 UTC) → #1077 (zoobc.how, 2026-10-27 00:42 UTC): Seed article updated
…
A batch is one transaction that carries several actions of one kind. Three kinds exist:
+ - ZBC payments, up to 25 in one batch;
+ - token transfers, up to 32, of any tokens, with the fee paid in ZBC;
+ - storage proofs, up to 1,000, one batch per node per storage epoch (see [[storage-pool]]).
− - ZBC payments;
− - token transfers;
− - storage proofs, one batch per node per storage epoch (see [[storage-pool]]).
+ A batch is all or nothing. Every action is checked up front, so either every payment in it happens or none does, and the whole batch is signed once.
− A batch is all or nothing. Every action is checked up front, so either every payment in it happens or none does, and the whole batch is signed once. The largest batch allowed is measured against the chain's compute ceiling per byte.
### What a batch costs
+ Several actions pay as several transactions. A batch's minimum fee is the sum of the minimum fees its actions would pay as separate transactions: a base fee for each action plus each action's byte charge (see [[fees]]), with the batch's message charged only once. Three payments without a message cost the same in one batch as in three single transactions. A batch of storage proofs pays nothing: each storage proof is a fee-free duty, so the sum is zero.
− Several actions pay as several transactions. A batch's minimum fee is the sum of the minimum fees its actions would pay as separate transactions: a base fee for each action plus each action's byte charge (see [[fees]]). Three payments in one batch cost the same as three single payments. A batch of storage proofs pays nothing: each storage proof is a fee-free duty, so the sum is zero.
+ What a batch saves is mostly work for the network, not fees: one signature to verify and one slot in the block instead of three. And it is the way for one account to pay many recipients in the same block.
− What a batch saves is work for the network, not fees: one signature to verify and one slot in the block instead of three. And it is the way for one account to pay many recipients in the same block.
> [!design] **Planned design.** Mixed bundles, which would combine actions of different kinds in one transaction, are planned only for a concrete need, such as the market's "replace order".
…