Propose a Safe transaction from a WalletConnect app

Follow a test transaction from a wallet app to the Safe queue and see where owners review and confirm it.

Before you start

KeySigner on iPhone and a WalletConnect-enabled app

  • Use Safe 1.3.0, 1.4.1 or 1.5.0. Check the network and that your KeySigner key is a current owner. Execution requires the Safe's configured number of owner confirmations.
  • Keep KeySigner open on your phone to receive plain-message, typed-data or transaction requests. The app must offer WalletConnect on Ethereum, Base, Arbitrum One, OP Mainnet, Polygon, Sepolia or Base Sepolia.
  • Check the Safe version

Data and access

Shared or checked
The wallet request identifies a Safe and carries proposed transaction details. The Safe owner reviews the destination, value and action before it goes to the proposal queue.
Check separately
The Safe’s configured owners still have to meet its threshold. Check execution and the final receipt independently.

Who does what

App user
Connects the test Safe and starts a request from the intended app and chain.
Safe owners
Review and confirm the same proposal. Only eligible owner confirmations count toward the Safe’s threshold.
Executor
Submits the authorized proposal for execution and checks its network receipt if you carry out the test transfer.
Remaining owners
Keep enough independent wallets to satisfy the current threshold if one owner is unavailable. Disconnecting the app does not remove a Safe owner.
  1. Add a test Safe

    In KeySigner, open Safes and add the address and network of a test Safe. Use a Safe on a supported network with version 1.3.0, 1.4.1 or 1.5.0 and at least one KeySigner key among its owners.

    Check. The Safe in KeySigner shows the test address and network. In Safe, match the owner address for your KeySigner key.

  2. Share the Safe with the test app

    Choose WalletConnect on the wallet app’s site. In KeySigner, open Accounts, tap Add (+), then choose Connect a dapp. Scan or paste the code, check the site's domain and requested network, and share only the test Safe.

    Check. The test app shows the shared Safe address. Check the session in Connected apps for the intended site and network.

  3. Compare the proposal and confirmations

    Submit a harmless test request. Review it in KeySigner, then compare the proposal and required number of confirmations in Safe. After the test, end the session from Connected apps.

    Check. The proposal appears in Safe with the expected details and confirmation count. After disconnecting, the session is no longer listed in KeySigner.

Check your result

A request from the wallet app becomes a proposal. The Safe still needs its configured owner threshold before execution. Compare the final transaction with the reviewed proposal if you execute it.

How to verify your setup

If you get stuck

The proposal is missing or still waiting

Check the network selected in both apps and which Safe you shared. Keep KeySigner open while the request arrives. In the Safe queue, confirm that the remaining required owners have approved before trying to execute.

Report a problem with this guide

Explore all setup guides →