Execute Safe transactions with fewer steps

Ambire’s Transaction Builder makes it easier to prepare and execute transactions.

You can start a batch and combine multiple actions into one Safe transaction. This reduces the number of calls and confirmations required from Safe owners, especially for multisig accounts.

For example, imagine a 2/3 multisig treasury preparing a rebalance:

Normally, this workflow would require separate transactions, each needing multisig confirmations. With batching, the entire sequence can be prepared in Ambire and executed as one Safe transaction.
​

Ambire supports EIP-5792, a standard that allows compatible apps to send batched actions directly to the wallet. Protocols like Uniswap, Jumper, and Bungee already use this communication method. Instead of triggering multiple wallet prompts, the app can send the entire interaction as a single batch.
​

Unlike other wallets with Safe integrations, such as Rabby, which may require executing each step as a separate call, Ambire allows you to bundle multiple actions into a single Safe transaction. Instead of signing each step individually and repeating the multisig confirmation process for each call, owners can approve the entire workflow in one go.
​

This opens the door to batching operations such as multi-send, multi-swap, batch revoke, approve-and-swap, and harvesting rewards from multiple places… or combining several of these actions into a single Safe transaction, as long as they are on the same network.
​

Ambire also simulates transactions before execution and shows the expected balance changes directly in the dashboard. Safe owners can review the outcome of a batched transaction and see their future token balances before signing.
​

Ambire simplifies how Safe owners sign and execute transactions.

Consider a 2/2 Safe multisig where both owner keys are imported into Ambire, for example, a Ledger device and another wallet. When executing a transaction, Ambire guides the user through signing with both keys and broadcasting the transaction in a single flow.
​

In another scenario, imagine a 2/3 Safe multisig where one owner signs the transaction elsewhere. Once the transaction reaches Ambire, the remaining owner key can approve it and broadcast it immediately.
​

This approach keeps the Safe security model intact while making multisig execution smooth and fast.
​
​

When executing Safe account transactions in Ambire, the gas fee is covered by an Externally Owned Account (EOA) in the wallet that broadcasts the transaction.

This account can be:

The Safe itself remains the account performing the transaction, while the broadcasting EOA simply covers the execution cost.