META - Transaction Orchestration

[Dominik1999]

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

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

[Dominik1999]

Guardian should know about all transactions (we need to create an issue about it). The basic unit of the Guardian should be a transaction