< Back to Newsroom

SSP Wallet v2.1.1: Enterprise Signing Restored

·3 min read·By SSP Editorial Team
SSP Wallet v2.1.1 release cover

SSP Wallet v2.1.1: Enterprise Signing Restored

Version 2.1.1 shipped on 21 August, a hotfix for the release that brought Solana to mainnet. It fixes one bug that stopped enterprise signing outright, and two smaller ones that made approvals harder to read than they should be.

If you use SSP Enterprise vaults, this is the update you want.

Opening a vault proposal sent the wallet to the error screen

The serious one. Between v2.1.0 and this fix, opening an enterprise payment proposal for signature could throw the extension to its error screen before the approval dialog ever appeared. The proposal was fine. The vault was fine. The wallet simply refused to show you the thing you were trying to sign.

The cause is a good illustration of how a bug can hide in code that looks unrelated. SSP Wallet handles several kinds of incoming request — a payment to approve, a message to sign, a Flux node to start — and those dialogs stay mounted in the background while another request is handled. Because they stay mounted, their props keep whatever the last request put there.

Flux node-start requests carry delegate public keys as a JSON string. Payment proposals fill the same slot with recipient objects. So when an enterprise proposal arrived, the node-start dialog was still listening, read a list of recipients as though it were a list of delegate keys, and crashed on the mismatch.

The fix is in two parts. The node dialogs now render nothing at all unless they are the active request, rather than quietly holding stale props. And the delegate list is type-filtered, so only actual strings are treated as keys. There are new contract tests around the shared dialog state to keep the two request types from confusing each other again.

Nothing was ever at risk here — a crashed dialog cannot sign anything, and moving funds needs both devices regardless. But it blocked signing entirely, which for a vault is its own kind of problem.

Website approvals open a window again, not a side panel

When a website asked for an approval, the request was arriving in a full-height side panel rather than the compact floating window. That hid the page you were signing for behind the thing asking you to sign, which is precisely backwards: you need to see the site to judge the request.

Web-page requests now open the compact window again. Opening the wallet yourself from the toolbar icon is unchanged and still follows your Popup, Window or Side Panel preference — this only affects approvals a site asks for.

Requests reach the wallet you already have open

Two smaller annoyances in the same area. A wallet window hidden behind the browser now comes to the front instead of answering somewhere you cannot see, and an open side panel no longer ends up with a second wallet window opening beside it after the browser has been idle.

Getting the update

Browser extensions update themselves, so most people will already be on v2.1.1 — check via the extension's settings if you want to be sure. Nothing needs re-configuring and no keys are affected.

Enterprise vault holders who ran into the signing crash: it is gone, and the proposals that would not open will open now.

For what shipped in v2.1.0 itself, see Solana Mainnet Arrives in SSP.

Share this article

Related articles