Safe Accounts
A Safe can hold a private balance in the Privacy Boost app. Moving tokens from the Safe into it is called shielding. From the private balance, the Safe can send privately to other Privacy Boost accounts, unshield back to a public address, swap, or use Earn. Any one owner can sign in with their own wallet to see the balance and history. Moving funds works the way it always does for your Safe: every shield, send, unshield, Earn action, and swap is a Safe transaction that needs your usual number of owner signatures. Privacy Boost has no key that can spend from the account.Before you start
- The Safe has to be on version 1.3.0 or later. A Safe on a version after 1.4.1 shields from inside Safe{Wallet}, not from app.privacyboost.io in its own tab.
- Use OP Mainnet, Base, or the Base Sepolia testnet, where Safe{Wallet} can queue transactions. On other Privacy Boost networks, such as Soneium and OP Sepolia, only a Safe with a threshold of one works, and it can’t shield.
- As with any Safe transaction, the owner who executes it pays the gas.
Sign in
Each owner signs in with their own wallet, either a browser wallet or one connected over WalletConnect. Don’t connect the Safe itself to the app over WalletConnect; if you do, the app stops and asks you to sign in as an owner instead. Signing in is a gasless message and doesn’t involve the other owners.From app.privacyboost.io
- Go to app.privacyboost.io, choose Connect wallet, and check the network under the wallet list.
- Choose Safe (Sign in with an owner wallet).
- Enter the Safe’s address.
- Connect your owner wallet and approve the sign-in message.
From inside Safe{Wallet}
- In Safe{Wallet}, connect an owner wallet using Connect at the top right, on the Safe’s network.
- Open Privacy Boost from Apps. If it isn’t listed, add
https://app.privacyboost.ioas a custom Safe App. - The app picks up the Safe that opened it. Connect your owner wallet and approve the sign-in message.
Set up the account
The first time an owner signs in, the app walks through Create a private account:- Save a recovery phrase. This is optional. Owners don’t need it to sign in, and any owner can show it again later from the profile menu. The phrase gives read access to the account. It can’t move funds.
- Store the account’s keys. Approve two signature requests in your wallet. After this, any owner can finish setup from any device.
- Create the account on chain. Choose Queue setup to your Safe, which queues a one-time Safe transaction. Share it with Copy link for co-owners, then sign and execute it in Safe{Wallet} with your usual number of owners. Even if you’re the only signer needed, you execute it yourself in Safe{Wallet}. On a network where the app can’t queue to Safe{Wallet}, a Safe with a threshold of one gets Run setup from your Safe instead, which runs right away.
Shield
Choose Shield, pick the token and amount, and confirm. You sign once to queue a single Safe transaction with everything the shield needs: wrapping native ETH if you’re shielding ETH, the token approval, and the deposit. In the Safe queue, it ends with arequestDeposit call to the Privacy Boost pool. A shield isn’t private the way a spend is: the token and amount are visible in the transaction.
Once enough owners have signed, any owner executes it in Safe{Wallet}. The funds leave the Safe when it executes, and the private balance updates on its own shortly after. Until then, every owner can see the queued shield under Safe approvals.
When you shield from inside Safe{Wallet}, Safe{Wallet} opens the transaction for review right away.
Send, unshield, earn, and swap
- Fill in the details and choose Queue approval (Queue to Safe for a swap, Confirm deposit or Confirm withdraw for Earn).
- Check the review sheet. It shows what the spend does, the amount, the recipient, and a commitment that ties the approval to exactly these details. The app checks the commitment before it lets you continue. Choose Continue to Safe.
- Sign once in your wallet to queue the approval in the Safe. Copy link for co-owners gives the others a direct link to it.
- The other owners check the approval in Privacy Boost (see below), then sign it in Safe{Wallet}. Once enough have signed, any owner executes it.
- Once it executes, Privacy Boost submits the private transaction automatically.
Checking an approval before you sign
In Safe{Wallet}, an approval is anapproveSpendBatch call to the Privacy Boost AuthRegistry contract. It doesn’t show the token, amount, or recipient, which is what keeps the payment private, but it also means Safe{Wallet} alone can’t tell you what you’re signing.
Before you sign another owner’s approval, sign in to Privacy Boost and open Safe approvals. Each pending approval lists its token, amount, recipient, expiry, and commitment, and its Queue position once the app finds it in the Safe queue. The queue position is the Safe transaction’s nonce, so make sure that’s the transaction you sign. Open in Safe{Wallet} takes you straight to it.
While an approval is pending
An approval expires 72 hours after it’s queued. If the Safe doesn’t execute it by then, nothing is spent, but the expired transaction keeps holding up the Safe queue until it’s cleared (see Safe approvals). The funds a pending approval would spend are set aside, and the balance shows how much is reserved. Earn and swap approvals also commit to a minimum output. If the price moves past it before the spend goes through, the spend waits under Price moved until the price comes back, you discard it, or it expires. Unshields, swaps, and Earn actions go out a random one or two blocks after the Safe executes the approval, which isn’t enough to stop someone linking the two by timing.Safe approvals
The Safe approvals button at the top right shows what’s waiting on the Safe. Open it to see the queue:
Discard drops a pending spend in Privacy Boost. Its Safe transaction stays in the Safe queue and holds up later Safe transactions, so reject it in Safe{Wallet} too. Reject rather than Remove: removing a transaction from the Safe queue doesn’t cancel signatures owners have already given.