How wallet integration works
The wallet submits the transaction to Safenet for checking and displays the result to the user. A typical flow is:- A user creates or reviews a Safe transaction.
- The wallet submits the transaction to Safenet for checking.
- Safenet evaluates the transaction and returns a result.
- The wallet presents the result as part of transaction review.
- Where Guard enforcement is enabled, a valid secure Validator attestation is required for normal execution.
Checks-only integration
Safenet checks can be integrated without enabling the Safenet Guard. In a checks-only integration, the wallet surfaces the Safenet result to the user but does not change the Safe’s onchain execution requirements. The wallet should clearly communicate whether the transaction:- Receives a secure result.
- Receives an insecure result.
- Enters arbitration because Sentinels disagree.
- Cannot be checked reliably.
Guard-enforced integration
Wallets can also integrate Safenet with the Safenet Guard. The Guard must first be enabled on the Safe before it can enforce Safenet attestations. With Guard enforcement enabled, a valid secure Validator attestation becomes an additional requirement for normal execution. The Safe’s existing signature threshold and other execution requirements continue to apply. Transactions without a valid secure attestation cannot execute through Safenet. Safe owners retain ultimate control through the separate delayed execution path. See Safenet Guard for the enforcement model.Safe Wallet integration
Safenet checks are planned for Safe Wallet. The rollout is planned in stages:- Checks-only: Surface Safenet checks and results during transaction review.
- Guard enforcement: Add onchain enforcement through the Safenet Guard.
Integrate Safenet
Safenet is permissionless, so no approval is required to integrate it. Wallet providers that want integration support can reach out.Safenet checks
See which transaction risks Safenet evaluates.
Safenet Guard
See how Safenet results are enforced onchain.