SSP Wallet v2.0 is the biggest release in the project's history: the entire wallet and the entire mobile Key rebuilt on a new design system, with a Portfolio home screen, one-approval multi-chain sync, and a pairing verification code that lets you prove your two devices were never tampered with. Nothing about your keys changed — updating in place keeps your wallet, your pairing, and your settings exactly as they were.
Both apps shipped on 11 August 2026: SSP Wallet v2.0.0 for Chrome and Firefox, and SSP Key v2.0.0 for Android and iOS.
Zero migration, same two keys
Start with the part that matters most, because a "2.0" in crypto usually means a migration, a new contract, or a funds move.
This one does not. There are no changes to how transactions are signed or how your seed is stored. Your addresses are the same addresses, derived along the same paths, so nothing needs to move and nothing needs re-deriving. Your pairing survives the update. The refactor behind the redesign was verified by an independent audit across every commit in the release — including token-level proof that a very large internal refactor changed exactly zero signing behaviour.
The security model is untouched: two keys, on two devices, both required for every transaction. If that model is new to you, start with what 2-of-2 multisig actually is.
A complete redesign
Every screen in both apps now runs on the new SSP design system — amber, Inter, Lucide icons and the pillar mark — in both light and dark mode.
The navigation changed shape. Wallet and chain switching now live in a single identity pill at the top, with a compact tab bar below, so the two things you switch between most often are always one tap away.
The wallet switcher also shows the balance of every wallet, served from local storage rather than fresh network calls — so opening it is instant even with a dozen wallets and no connection.
Onboarding was rebuilt end to end: name and colour your wallet, verify your seed with a word challenge instead of a checkbox, then pair with live progress instead of a spinner. Settings became Menu — everything from the old scattered menus in one place. The built-in tutorial was rewritten to match the new interface.
Portfolio — your new home
The wallet now opens on the Portfolio tab: your total balance across every chain, tokens included, with 24-hour change and allocation at a glance. Previously you landed on a single chain and had to go looking for the rest.
A fresh wallet doesn't open on an empty chart — it routes you straight to receiving your first funds.
Privacy mode, introduced in v1.40.0, is now a tap on your balance: it blurs every amount on screen for the moments when someone is standing behind you or you're sharing a screen.
Activity gets its own tab
Transaction history used to be a section bolted onto a chain view. It is now a dedicated Activity tab, so "what happened to my money" is a destination rather than something you scroll to find.
One approval for every chain
This is the change that will save the most taps. Activating chains used to mean one approval on your SSP Key per chain. Now you select any set of chains and approve them all with a single confirmation, with live progress on both devices.
On first sync, the most popular chains come preselected: Bitcoin, Ethereum, BSC, Flux, Dogecoin, Zcash, Bitcoin Cash and Litecoin. Testnet networks moved behind a toggle in Settings and are off by default, so a new wallet is no longer a wall of options.
A verification code for your pairing
After syncing, both devices display the same six words, derived from your keys. If the words match, no one — not even the SSP relay that carried the messages between your devices — could have tampered with the pairing. Your Key can also scan the wallet's code to verify automatically.
This closes a gap that every paired-device system has and few make visible: the moment of pairing is the moment worth attacking, and until now you had to take it on trust. Because the words are derived from the key material itself rather than from anything the relay sends, a relay that altered the pairing could not produce a matching pair of codes. Six words is a small ceremony for eliminating an entire class of attack.
Unified Send and the 2-of-2 handshake
Sending is now one flow for every chain: compose, review, approve. The full recipient address is always shown at the review step — never truncated at exactly the point where truncation is what an address-swapping attacker is counting on.
The approval step gained a 2-of-2 handshake screen that shows your two devices co-signing in real time. The co-signing was always happening; now you can watch it happen, which makes the thing SSP does differently visible instead of invisible. If you want the deeper version of why one signer on two devices beats one key on one device, we wrote that up in single-signer multisig.
Buying, selling and swapping
Both flows were rebuilt on the new design system, and both are worth understanding precisely rather than vaguely.
Buy and sell run through an on-ramp provider embedded in the wallet, with the destination address signed by the SSP relay so the provider cannot be handed a different address than the one you chose.
Swap is not a DEX. It price-compares centralized instant exchangers and settles as an ordinary 2-of-2 send to the chosen exchanger's deposit address — which means no router, no token approvals, no slippage setting and no MEV exposure, but a custodial window while the exchanger holds your funds. That distinction is the whole risk profile, and we explain it in full in buy, sell and swap explained.
The side panel, redesigned
The side panel — which keeps SSP docked beside a dApp instead of collapsing every time you click away — was rebuilt on the new design system too, Portfolio and all.
Everything in one Menu
Settings became Menu, and the reorganisation is the point: chain management, testnets, privacy mode, contacts, the tutorial and backup health all live in one place instead of being scattered across screens that each owned a piece of the configuration.
Backup health deserves a specific mention. The wallet now reminds you what is at stake until your seed is verified and your Key is paired — not as a one-time dismissible banner, but as a standing state until the thing is actually done.
Flux node management came along for the redesign as well, with a clearer nodes table and delegate actions.
On your SSP Key
The mobile app got its own set of changes, several of which are security-visible.
Slide to approve. Every signature is now a deliberate gesture rather than a tap. Release early and nothing happens — there is no way to sign by reflex or by accident.
Clearer approvals. Every request type shares one clean layout with plain-language summaries decoded on your device, never trusted from the network. Token approvals warn loudly about unlimited allowances and collection-wide NFT operator grants, and name the spender asking for them. These are the two approval patterns behind a large share of wallet-drain losses, and they now look alarming instead of routine.
Signing history. A local, encrypted, biometric-gated log of everything this Key has co-signed. It never leaves your device. Privacy mode masks identities in that history at a tap.
Real backup verification. Creating a new Key now ends with a word challenge instead of an "I backed it up" checkbox. If you have ever ticked that box without writing anything down, you already know why this changed — and seed phrase best practices is worth ten minutes.
The app also lost about 6 MB of unused icon libraries and duplicate assets, and motion now respects your system's reduce-motion setting.
Under the hood
All chain backends now run on branded *.sspwallet.io endpoints with built-in failover, in both apps.
Every dependency was updated and exactly pinned, and every fixable vulnerability resolved. The wallet continues to ship deterministic builds with GPG-signed checksums, so you can rebuild v2.0.0 from source and confirm you get the same bytes we published.
Updating
Chrome and Firefox update the extension automatically; you can force it from your browser's extension page. SSP Key updates through the Play Store and App Store.
You can update in either order. Wallet v2 works with Key v1, and Key v2 works with Wallet v1. Batch chain sync and password recovery via your SSP Key switch on once both apps are on v2 — everything else works immediately.
Nothing is required of you beyond updating. No migration, no re-pairing, no moving funds.
