Batch Routing

Batch Routing groups compatible queued operations into one release workflow.

How it works

Batch Routing is used with Controlled Mode. Operations enter the queue first; Automatic Mode does not wait in that queue.

Create compatible operations
  |
  v
Add them to the privacy queue
  |
  v
Review the batch
  |
  v
Release the batch
  |
  v
Process each destination

Compatibility

Operations can be batched only when their routing and release requirements are compatible. The app determines whether queued operations can be grouped.

Compatibility may depend on:

• Vault and operation type
• Routing configuration
• Release configuration
• Destination requirements

Governance

For a Private Multisig, every required approval must be complete before an operation becomes eligible for release. Batching never bypasses the vault’s approval rules.

A Personal Vault does not require multisig approvals, but its queued operations must still satisfy the same compatibility checks.

Individual and batch release

Individual release:

Operation A -> Release A
Operation B -> Release B
Operation C -> Release C

Batch release:

Operations A, B, and C
  |
  v
One reviewed batch
  |
  v
Coordinated release

Batching changes how compatible operations are organized and released. It does not change wallet approvals, vault authorization, or blockchain finality.