On 2025-03-15, SSP Wallet v1.17.0 ships two things at once: a Firefox build (in beta) so Firefox-family users can run the wallet, and a quieter UX change to how SSP handles a device-fingerprint change — the moment its strong device-specific encryption notices that the machine it's running on isn't the one it was set up on. The first story is reach; the second is making a security guarantee less abrupt without weakening it.
Firefox support is here, in beta
Until v1.17.0, SSP Wallet shipped as a Chromium build — the same .crx running on Chrome, Brave, Edge, Opera, and the rest of the Chromium family. From this release on, the project also produces a Firefox build. Both come out of the same source tree at the same release tag.
One important caveat. The Firefox build is not yet submitted to the official Firefox Add-ons store, and the artifact distributed today is not signed through Mozilla's signing pipeline. While that submission is in flight, the distribution channel is the SSP GitHub Releases page — Firefox users download the build directly from there, as they would any other open-source release artifact.
Plain-language version: the code is the same SSP Wallet that's been audited, open-source, and shipping for Chromium users. The thing that's "beta" isn't the security model — it's the distribution. The Add-ons store takes over as soon as Mozilla's submission and signing path completes.
Why two builds matter
Multi-browser support sounds like a checkbox feature, but for a wallet it's table stakes. Crypto users pick a browser for reasons that have nothing to do with which wallet they want to run — privacy posture, extension ecosystem, employer policy, preference. Forcing users to switch browsers is friction that pushes people toward worse choices: a custodial app, a hot exchange balance, a "just for crypto" profile they never harden.
Chromium is a substantial userbase, but not everyone. Firefox is its own ecosystem with its own developer culture and its own community of privacy-leaning users — exactly the kind of people who reach a multi-asset multisig wallet because they want to self-custody. Shipping a Firefox build means SSP meets those users where they already are.
The plan is to keep the two builds in lockstep, releasing both at the same tag from the same source, until the Firefox build is in the store and stops carrying the "beta" label.
Smarter device-fingerprint change detection
The second story in v1.17.0 refines how SSP handles device-fingerprint change detection.
SSP Wallet uses strong, device-specific fingerprint encryption to protect sensitive material on the user's machine. The seed material and signing keys are encrypted with a key derived from properties of the device itself. If the device changes underneath the wallet — a new machine, a major OS shift, a hardware swap — that key no longer derives the same way, and the wallet cannot decrypt the sensitive bytes. By design.
Before v1.17.0, when SSP detected a fingerprint mismatch, it navigated the user straight to the welcome screen — the same screen new users see — which made the change feel abrupt and didn't always explain what had happened. From v1.17.0 on, SSP raises a notification about the detected fingerprint change. The notification spells out the situation: a device change was detected, and continuing requires restoring the wallet from the user's seed phrase. The path forward is the same — the user re-onboards with their seed — but the wallet now tells them why instead of just landing them on a fresh screen.
The security property has not changed. A fingerprint change still means the sensitive material on disk can't be decrypted by the wallet on the new device, and recovery still flows through the seed phrase. What v1.17.0 adds is better explanation of the event, plus an effort to preserve non-sensitive data — UI settings, address-book entries, theme preferences — across the re-onboarding so the user's environment looks familiar after they restore. A smoother transition through the same gate, not a different gate.
If you see this notification on a machine you haven't migrated, treat it as significant. Either the device fingerprint genuinely changed (in which case restoring with the seed is the correct response), or something is reporting different fingerprint properties than before — worth investigating before continuing.
Installing the Firefox build
For now, Firefox users install SSP from the v1.17.0 release on GitHub. The release page lists both the Chromium and Firefox artifacts side by side. Pick the Firefox build, follow Firefox's "install from file" flow, and the wallet behaves the same way it does on Chromium — with the same multisig setup that first shipped in the original SSP launch.
The Add-ons-store submission is in progress. When it finishes, a follow-up post will point at the official store URL. Until then, the GitHub release is the canonical install path for Firefox users.