WalletConnect is now available in Safe{Mobile}

WalletConnect is an open protocol that connects wallets to decentralized applications without exposing private keys, and it’s now live on Safe{Mobile}. For signers, proposers, and treasury leads who use a Safe together and aren't always at a desk, treasury work doesn't stop when people leave their desks. Signers still need to approve transactions, finance teams still need to propose payments, and protocol operators still need to respond when timing matters.

Start with the roles, not the tech

Picture a common setup. Three signers on the multisig wallet. Two approvals to move funds. One finance lead who can propose payments but not execute them. The finance lead prepares a transaction in a dapp. Two signers review and approve it, and only then does anything move. Nobody in that setup can act alone, and nobody has to trust that the others won't.

The Safe mapping comes second. That setup is a multisig wallet with three owners, a threshold of two, and a proposer added to the account. The policy lives onchain, so it holds no matter which app or device is used. Because Safe is a smart account, the account itself enforces the approval policy, not whichever wallet interface the team happens to use.

WalletConnect support in Safe{Mobile} removes the need to act on desktop, to connect the Safe to a dapp. Connect your Safe to any WalletConnect-compatible dapp from your phone, and the same multisig approval policy holds.

You can now use Safe{Mobile} as your mobile crypto wallet for connecting your Safe to WalletConnect-compatible dapps while keeping the same multisig approval policy.

What this gives your team

Segregation of duties. The person who prepares a payment is never the person who approves it alone. Proposers build transactions, signers approve them, and the threshold decides when execution is allowed. That separation now works from anywhere.

A complete audit trail. Every proposal, approval, and execution is recorded onchain and verifiable. When your auditor or community asks who approved a transfer and when, the answer is already written.

No single point of failure. No single key, person, or device can move funds. A lost phone or offline signer doesn't compromise the account. Authority is distributed across multiple owners, and transactions still require the configured threshold before execution.

How to run it from your phone

1. Connect your Safe to WalletConnect dapps by scanning the QR code or pasting the WalletConnect connection link into Safe{Mobile}. Your Safe becomes the connected account while keeping the same approval policy.

2. Propose the transaction where the work happens. Initiate the transaction in the dapp. It appears in Safe{Mobile} as a pending transaction, waiting for approvals rather than executing on its own.

3. Collect approvals against your threshold. Each signer reviews the transaction details and signs. Nothing moves until the threshold you configured is met.

4. Execute. Once the required approvals are in, execute directly from Safe{Mobile}. The result is the same policy you set on day one, enforced from a phone.

Connect your Safe to WalletConnect in Safe{Mobile} and execute from wherever you are.

Verify before you connect. WalletConnect opens your Safe to any compatible dapp, including ones that spoof a legitimate project. Check the dapp's URL against its official source before connecting, and review the transaction details in Safe{Mobile} before signing, rather than trusting what the dapp displays. The threshold still protects against one compromised signer, but it doesn't replace checking what you're about to approve.

FAQ

How many signers should a DAO treasury have?

Most teams run three to seven signers with a threshold above half, such as 2-of-3 or 3-of-5. Enough signers that no individual controls the funds, few enough that approvals don't stall. Larger treasuries often split funds across multiple Safes with different signer sets for daily operations and long-term holdings.

Can I use WalletConnect with a multisig?

Yes. Safe multisig connects to any WalletConnect-compatible dapp, from Safe{Mobile} or from Safe{Wallet}. The connection doesn't change your security model: every transaction still requires the approvals your threshold demands.

Can I execute Safe transactions from my phone?

Yes. Transactions initiated in a connected dapp appear in Safe{Mobile} for review, signing, and execution. Once the threshold is met, any signer can execute from the app.

Does every signer need Safe{Mobile}?

No. A Safe is one account with one policy, accessible from mobile and web. Signers approve from whichever surface they prefer, and the approvals count toward the same threshold.

The approval policy travels with the account, not with the desk. WalletConnect support in Safe{Mobile} means your multisig wallet can connect to WalletConnect dapps wherever your team is working. Set your roles once, and continue crypto treasury management from the same smart account, whether signers approve from desktop or mobile.

Safe{Labs}

20 July 2026

Copy link