META - Transaction Orchestration

Tracking issue for the Guardian's ability to handle the full transaction lifecycle. The user submits a TransactionSummary and signs it; the Guardian takes it from there — proving, batching, and committing.

Capabilities

• Prove & commit — Guardian receives a signed TransactionSummary, generates the ZK proof, and commits the transaction to the Miden network.
• Batch proving — Guardian collects multiple transactions, proves them as a batch, and submits.
• Instant settlement — In the future, the Guardian can settle immediately between several accounts using ephemeral notes, without waiting for on-chain finality per transaction.

Related issues

• #254 — Guardian proves & commits transactions on behalf of users
• #180 — Support delegated proving for operators
• #239 — Support batch proving of transactions
• #191 — Add a canonical nonce endpoint to skip unnecessary syncs

Start by reading the linked issues #254, #180, #239, and #191 to understand the planned transaction lifecycle and which capabilities are already scoped. Trace how the Guardian is expected to receive a signed TransactionSummary, prove or batch it, and commit it to the Miden network. Done means the tracking issue’s listed capabilities are implemented across the related work.