Safe Transactions

When Fordefi is one of the signers on a Safe{Wallet}, transactions and messages initiated through Safe pass through Fordefi for signing. Fordefi recognizes these as Safe-originated and presents them with full context, rather than as opaque contract calls or generic message signatures.

For information on adding a Safe wallet to Fordefi, see Connect a Safe{Wallet}.

When a transaction or message originates from Safe{Wallet} and Safe{Wallet} has been added as a vault, the Fordefi web console, mobile app, and browser extension display:

• Origin: The Safe{Wallet}.
• Underlying intent: The decoded action (for example, Transfer, Allowance, Contract call) — not just execTransaction or "message signature".
• Safe metadata: The Safe{Wallet} contract address, proposer address, transaction type, and operation mode (CALL or DELEGATECALL).
• Asset impact: Outgoing and incoming asset summary, based on simulation.
• Full decoded call data: Target contract, method name, and parameters.

Safe transactions are simulated by Fordefi prior to signing. The simulation summarizes the expected on-chain effects (asset transfers, contract state changes) so signers and approvers can confirm the intended outcome before approving.

When you are asked to sign a Safe transaction in Fordefi, the review screen shows:

• The Safe vault as the transaction origin.
• The Fordefi signer vault used to sign on behalf of Safe.
• The Safe's required signature threshold.
• The operation type (CALL or DELEGATECALL).
• A policy evaluation summary. See Safe Transactions in Policies.
• An outgoing and incoming asset summary.
• The full decoded call data.

Approve the transaction in your mobile device once you have confirmed the decoded intent matches the operation you expect.

Safe{Wallet} supports batching multiple operations into a single transaction (using Safe's multiSend contract). For batched Safe transactions, Fordefi presents the message signature without per-operation enrichment — individual operations within the batch are not decoded separately.

Once a Safe vault is created, only Safe transactions occurring from that point onward are tracked and enriched. Historical Safe transactions executed before the vault was added are not retrofitted in Fordefi.