SSP Wallet is built for people who want self-custody without the single point of failure that most wallets ship with. Instead of one device holding one key, SSP splits signing power across two devices — typically your phone and your browser — and requires both to approve every transaction. That model is called 2-of-2 multisig, and it is the core thing that makes SSP setup look slightly different from the wallet you may have used before.
This walkthrough takes you from a fresh install on both devices to your first confirmed transaction. Expect about fifteen minutes of focused setup, two seed phrases to write down, and a few new concepts along the way.
What you need before you start
Gather these before you open any app:
- A phone. iOS or Android, running a current OS version, with enough free space for one app install.
- A desktop browser. Chrome, Firefox, Brave, or Safari, all recent versions. The browser will host the SSP extension.
- Stable internet on both devices. Pairing exchanges data between phone and desktop; a dropped Wi‑Fi connection is the most common cause of setup hiccups.
- A way to write down two seed phrases. Pen and paper works. A metal backup plate works better. Two separate storage locations work best. See our guide on seed phrase best practices before you decide where these will live.
- Fifteen quiet minutes. Do not rush the seed-phrase confirmation step.
Step 1 — Install the mobile app
Open the App Store (iOS) or Google Play (Android) and search for SSP Wallet. The legitimate app is published by InFlux Technologies Limited. Check the publisher name before installing — there are several lookalike apps in both stores that copy the name and icon. The real SSP Wallet has tens of thousands of installs and a long review history; a brand‑new clone will not.
Tap install. When the app finishes downloading, open it but do not tap Create wallet yet. Leave the app on its start screen.
Step 2 — Install the browser extension
On your desktop, go to sspwallet.io and follow the link to the official Chrome Web Store, Firefox Add‑ons, or Safari Extensions listing. Again, confirm the publisher is InFlux Technologies Limited and that the listing has a meaningful number of users and reviews. Pin the extension to your toolbar after install so you can find it again easily.
Open the extension. You should see its start screen too. Both halves of your future wallet are now ready to talk to each other.
Step 3 — Pair the two devices
On the desktop extension, tap Create new wallet. The extension will display a QR code along with a short numeric pairing code. On the phone, tap Create new wallet and choose Pair with browser extension. Point the phone's camera at the QR code on your screen, or type the numeric code if the camera approach is fiddly.
The two apps now exchange public key material over an end‑to‑end encrypted channel. This is not the same as logging in. No SSP server is creating an account for you; nothing on either device leaves your control. What is happening is purely local: each device generates its own private key, and the two devices learn each other's public keys so they can later recognise a valid co‑signature.
When the pairing succeeds, both screens will show the same short fingerprint. Compare them. If they match, tap Confirm on both devices. If they do not match, cancel and start the pair again — a mismatch means another device intercepted the exchange, which is rare but worth checking for.
Step 4 — Generate the 2-of-2 wallet
With pairing confirmed, both apps will guide you through generating your wallet. Each device produces its own seed phrase, independently, using its own randomness. The phone shows twelve words. The browser extension shows a different twelve words. You need both.
Write down each seed phrase on its own sheet (or its own metal plate), label which device it belongs to, and store the two backups in different physical locations. The whole point of 2-of-2 is that a thief who steals one device — or one backup — still cannot move your funds. Storing both backups in the same drawer defeats that.
Each app will then ask you to confirm a few words from its seed phrase to prove you wrote it down. Do this carefully. When both confirmations pass, you have a working wallet whose signing keys live on two separate devices, and whose recovery material lives in two separate places.
Step 5 — Send your first transaction
Fund the wallet with a small amount first. Send yourself the smallest meaningful amount of whichever asset you plan to use — enough to cover network fees with a little to spare. Wait for it to arrive in the wallet before going further.
Now send a test transaction back out. From the desktop extension, tap Send, paste a recipient address you control (a second wallet, an exchange deposit address — anywhere you can verify it lands), and enter a tiny amount. The extension will show you the network fee, often called <span id="gas"></span>gas — the payment that goes to the validators or miners who include your transaction in a block. Higher gas usually means faster inclusion; lower gas means waiting longer or, on a congested network, not being included at all.
Review the recipient, amount, and fee carefully. Tap Sign. The desktop extension produces the first of two required signatures and pushes the half‑signed transaction to your phone. Your phone vibrates or shows a notification: open the SSP app and approve. The phone adds the second signature and the now‑complete transaction is broadcast to the network.
For a few seconds, the transaction sits in the <span id="mempool"></span>mempool, the network‑wide pool of valid but unconfirmed transactions waiting for a block. Once a validator includes it, you will see one confirmation. After enough additional blocks build on top of that one — the exact number depends on the chain — the transaction reaches <span id="finality"></span>finality, the point at which it is considered irreversibly settled. Your wallet UI will show the status changing from pending, to confirmed, to final.
Common first-time issues
Pairing did not complete. Almost always a network problem. Confirm both devices are online, close and reopen both apps, and try the pair again. If you are on a restrictive corporate Wi-Fi, switch to a phone hotspot for the pairing step only.
Mobile and desktop show different receive addresses. This is rare and means the pairing did not finish syncing. Do not send funds yet. Delete the wallet on both devices and re‑pair from scratch.
Transaction is stuck in the mempool. The fee was too low for current network conditions. On chains that support it, use the Speed up option in the extension to rebroadcast with a higher fee. Otherwise wait — most stuck transactions either get included eventually or drop out, at which point your balance is restored and you can retry.
Signing fails on the second device. Usually battery‑saver mode killing the SSP app in the background. Bring the app to the foreground, then re‑trigger the signature from the first device.
Next steps
You now have a working SSP wallet whose security depends on two devices agreeing, not on one device staying safe. That is the SSP differentiator. To understand why the two‑device model defends against the threats that drain ordinary single‑key wallets, read What is 2-of-2 multisig? next.
