How to use a Safe multisig with Rabby

Quick steps

1. Add an owner key. Connect a hardware wallet or import an owner key in Rabby.
2. Add the Safe address. Add a new address, choose the Safe multisig type, paste the Safe address and confirm the chains where it is deployed.
3. Propose a transaction. Select the Safe, use a dapp or send tokens, read the preview and sign with your owner key.
4. Collect signatures. Other owners review and sign the pending transaction in Rabby or Safe's web app until the threshold is met.
5. Execute. One owner executes the fully signed transaction and pays the network gas.

Safe (formerly Gnosis Safe) is a smart contract wallet that needs several owners to approve each transaction, for example 2 of 3. It is popular with teams, DAOs and individuals who want to remove single points of failure. Rabby has supported Safe since at least January 2022, when it published a guide to using Gnosis Safe with DeFi in Rabby (Rabby on Medium, January 2022), and it added Safe on Base in August 2023 (Rabby on X, August 2023).

How Rabby works with a Safe

• The Safe holds the funds. Its address is a contract, not a key.
• Owners sign. Each owner uses their own key manager. Rabby says you do not need to import an owner's private key or seed phrase if you use a key manager such as a hardware wallet (Rabby on Medium, 2022).
• Signatures are collected through Safe's transaction service. Rabby says it cross-checks the data from Safe's backend against on-chain data rather than trusting it blindly.
• Owners can sign in Rabby or in Safe's own web app, so a team can mix both.

Before you start

• An existing Safe. Rabby is an interface; create the Safe in Safe's own app if you do not have one.
• At least one owner key in Rabby. A hardware wallet is strongly recommended; see hardware wallets.
• The Safe's address and the chain it was deployed on. A Safe exists only on the chains where it was deployed.
• The genuine Rabby extension, checked with our verifier.

Step 1: add owner and Safe

1. Connect or import an owner key in Rabby, for example your Ledger or Trezor.
2. Add a new address and choose the Safe (multisig) address type. Older Rabby material calls it Gnosis Safe.
3. Paste the Safe address and, if asked, pick the chain or chains where it is deployed.
4. Confirm. The Safe now appears in your address list, and you can view its balances like any other address.

Step 2: propose a transaction

Select the Safe as the current address and connect to a dapp, or send tokens from it. When you confirm, the transaction is not sent directly. Rabby creates a Safe transaction (Rabby calls these tasks in its 2022 guide) and asks an owner key in your Rabby to sign it. That signature is the first approval.

Read Rabby's preview carefully. It shows what the Safe transaction will do. For the hardware owner, also check what the device asks you to sign.

Step 3: collect the other signatures

Other owners open the pending transaction, in Rabby if they added the same Safe, or in Safe's web app, and sign it. Each owner should check independently that the target, amount and action are what the team expects. Do not rely on a screenshot or a chat message.

Step 4: execute

When enough owners have signed to meet the threshold, any owner can execute the transaction. Executing is an on-chain transaction, so the executing owner pays the gas from their own address on that chain. After execution, the Safe's balance changes and the transaction leaves the queue.

Choosing owners and a threshold

The threshold is how many owners must sign. A 2 of 3 Safe survives the loss of one key, and an attacker needs two keys. Put each owner key on a different device type or with a different person, so one failure cannot reach the threshold. Avoid a threshold equal to the number of owners, because losing a single key then locks the Safe. Owners and threshold are changed through Safe transactions, which need the current threshold to approve.

Tips and cautions

• Verify on several devices. In the February 2025 Bybit theft, attackers tampered with a Safe web interface so signers approved a malicious transaction that looked normal. Owners should check details on their hardware screens and in a second interface.
• Nonce order matters. Safe transactions execute in order. A stuck earlier transaction blocks later ones until it is executed or replaced.
• Same address, different chains. A Safe at the same address on another chain may not exist or may have different owners. Never send funds to a Safe address on a chain where it is not deployed.
• Mobile. We could not confirm Safe support in the Rabby mobile app as of October 2026. Check in-app, or use the extension.

Alternative: Rabby as an owner in Safe's web app

You can also do the reverse: open Safe's web app and connect Rabby as the browser wallet for an owner address. Rabby then signs owner confirmations, with its simulation and warnings still shown for each request. Many teams use this when some owners do not use Rabby.

Frequently asked questions