Summary

To unlock gas savings via transaction aggregation, da-builder needs a way to submit proof transactions as if they originate from your EOA. For Aztec Ignition, this means da-builder can submit proofs on your behalf and Aztec will attribute the transaction to your EOA (i.e., msg.sender remains your EOA for attribution and protocol logic).

There are multiple ways to do this with different security/operational tradeoffs. We recommend starting with a time-boxed, low-exposure test on a subset of dedicated prover EOAs.

Mechanism: EIP-7702-Style Delegation

We can enable “EOA-originating” calls by delegating your EOA to a compatible smart contract wallet (EIP-7702-style delegation). This preserves msg.sender while allowing execution logic to be constrained in code.

Proposer Models

Option 1 - Trusted Proposer

What it enables: da-builder can execute transactions broadly on your behalf.

Pros

• Fastest integration
• No changes to signing and operations

Cons

• Large blast radius: if compromised or misused, it could act with full EOA authority

When appropriate

• Dedicated prover EOAs only
• Minimal ETH balances
• No other valuable permissions attached to those EOAs

Option 2 - Trustless Proposer

What it enables: da-builder can only submit transactions that you have signed.

Security properties