The single biggest product story SSP has shipped lands across four releases over six weeks. v1.33.0 on 2026-02-05 plants the flag — SSP Enterprise, self-custody multisig vaults for businesses and teams, opens its doors. v1.34.0 on 2026-02-28 lands the actual signing surface — vault transactions on UTXO and EVM chains, ERC-20 tokens included, with a transaction-review UI that names the vault, the organization and every counterparty. v1.35.0 on 2026-03-10 widens Enterprise support and ships deterministic builds for Chrome and Firefox. v1.36.0 on 2026-03-21 polishes the handling and defaults new installs to the Side Panel. The product page is live at sspwallet.io/ssp-enterprise.html.
SSP Enterprise enters the room (v1.33.0, Feb 5)
A wallet that has been about individuals — two devices, one human, one signature each — opens up to a new shape of user: an organization. Businesses, treasury teams, DAOs, funds, OTC desks, any group that holds crypto on behalf of more than one decision-maker needs what the lone-user wallet cannot give them: multi-party approvals, an org-level view of who can do what, transaction alerts that fan out to a list of people, and portfolio analytics the finance lead can pull without anyone's seed.
v1.33.0 ships the first surface of that product. The wallet announces SSP Enterprise — "self-custody multisig vaults for businesses and teams" — with the supporting product page, and starts wiring the extension to talk to it. The release also brings quieter UX upgrades: an improved SidePanel, smoother window opening, and tighter Settings defaults. None of those are the headline. The headline is that SSP now has an answer when a team asks how their treasury fits in.
Self-custody, multi-party
The architecture is the same one SSP shipped in v1.0.0 — covered in Introducing SSP Wallet — true 2-of-2 multisig goes live — only the cardinality changes. The wallet was always built on multisig at its root, not bolted on. Enterprise raises the M and N. A vault can require multiple signers from a defined set, with org-level rules about who is in the set and what they may approve. The custody model stays self-custody: nobody at SSP, RunOnFlux or anywhere else holds your keys, signs on your behalf, or can freeze your funds.
What Enterprise adds around the primitive is the organizational scaffolding. Organizations hold vaults; vaults hold approval policies; policies decide which signers, in which combinations, can move which assets. Transaction alerts notify the relevant people when a proposal lands. Portfolio analytics let a finance owner see the position across vaults without ever touching a key. The signature stays on the device with the signer; the coordination becomes the product.
Vault signing arrives (v1.34.0, Feb 28)
Three weeks later, v1.34.0 lands the actual signing surface. The wallet extension can now sign Enterprise vault transactions directly — on UTXO chains (Bitcoin, Flux, Litecoin and the rest of the UTXO family) and on EVM chains starting with Ethereum. The review UI is built specifically for the vault flow: it shows the vault name, the organization, every recipient with amounts, the network fee and the memo before you sign. No raw payloads. No squinting at hex.
Enterprise tokens come with it. ERC-20 transfers from a vault now decode with the correct symbols and decimals, building on the ERC-20 backbone from More ETH tokens, CSV export and Brave support and the EVM range mapped out in EVM expansion — Polygon, BSC, Avalanche join SSP. A vault holding a stablecoin, a governance token and ETH on the same chain renders all three the way the personal wallet has rendered them since v1.18.0 — right symbol, right decimals.
WK Identity — the 2-of-2 you can prove
v1.34.0 also surfaces something subtle: the SSP WK Identity. It is the 2-of-2 multisig address derived from your wallet, displayed in the wallet's details panel with a QR code and a copy button. It is not a balance; it is an identity. It is the address that proves you are who you say you are — the same key material that secures your funds, used as the public handle by which Enterprise systems recognize you.
This matters because Enterprise needs to know which signer is which without anyone trusting an email address or a username on its own. The WK Identity gives the protocol a self-custody-native answer. It is yours because you control the keys that derive it; it is verifiable because anyone can ask you to sign with it.
Email notifications, with cryptographic proof of you
The same release adds Enterprise email notifications, and the way they enrol is worth noticing. From Settings, you subscribe an email address; SSP verifies the address by sending a code; and the subscription is then tied to your WK Identity through a signature. The server stores not just "this email subscribed" but "this email is bound to this self-custody identity, proven by a signature against the WK key." Unsubscribing follows the same proof.
The result is a notification feed that cannot be hijacked by anyone who does not hold your keys. If a proposal needs sign-off, the alert reaches the address tied to your identity. If you ever change devices, the same proof reattaches you to the same feed.
v1.35.0 + v1.36.0 polish (Mar 10 + Mar 21)
v1.35.0 widens Enterprise support — more flows, more chains, more edge cases handled cleanly — and ships another release first established in SSP releases go fully reproducible — deterministic builds and GPG. Enterprise inherits it from day one: every Enterprise-capable build of SSP, on Chrome and on Firefox, is byte-for-byte reproducible from public source.
v1.36.0 then sands the rough edges. Enterprise handling improvements clean up signing flows, error states and the panel transitions. New installs default to the Side Panel — already SSP's recommended layout — so the wallet is permanently visible next to the dApp or Enterprise dashboard you are working with.
What this means for self-custody at scale
For years, "self-custody multisig" and "team treasury" lived in different worlds. Teams that wanted multi-party approval reached for a custodian; teams that wanted self-custody dealt with bespoke smart-contract wallets they had to babysit. SSP Enterprise puts the two in the same wallet. The signing surface is the one signers already know. The keys never leave the devices. The custody is yours. What scales is the coordination around it — and that is exactly where a product can help.