v1.31.0, shipped on 2026-01-05, turns SSP into the operator's wallet for the Flux network. The release lands Flux delegate support — node operators can now run, view, and act on delegate assignments from inside SSP — and pairs it with a start-all-nodes control that fires every owned node in a single tap. Alongside the operator features, swap users get a long-requested max button and the asset-switch bug that ate target-chain paths is fixed. Together it is the most operator-focused release SSP has shipped since parallel-asset claiming introduced Flux mechanics to the wallet.
Flux delegates land in SSP
A Flux node operator does not always hold the underlying collateral themselves. Delegation is the mechanism the Flux network uses to separate who owns the stake from who runs the hardware: an owner pledges collateral and assigns it to a delegate who actually runs the node, and rewards flow back to the owner while the delegate keeps the infrastructure online. Delegation is what lets the network scale operator capacity without forcing every node operator to also be a holder, and vice versa.
Until v1.31.0, SSP could see Flux balances and claim parallel assets, but it could not participate in the delegate flow itself. v1.31.0 adds it as a first-class surface. From the Flux account screen the wallet now shows the delegates an owner has assigned, the delegate addresses the wallet is currently acting for, and the actions that move state between them. The signing flow is the same multisig flow used everywhere else in SSP — the SSP Key co-signs the delegate operation the way it co-signs a swap or a send. There is no separate trust model for Flux: a delegate action is just another transaction the wallet builds, the SSP Key approves, and the network confirms.
The effect is that anyone running Flux infrastructure can now manage that infrastructure from inside the same wallet that holds their everyday balances. The operator does not need to leave SSP, switch to a CLI tool, or move funds to a single-sig key to sign a delegate transaction.
Start all nodes, in one tap
The companion feature is the start-all-nodes control. Operators who run multiple Flux nodes used to start them one at a time — open the entry, sign, repeat — which scaled badly as fleets grew. v1.31.0 collects every node the wallet has visibility into and offers a single action that starts the lot in one signed batch.
It is small and obvious in hindsight. The point is that operator UX in SSP is now shaped by people who actually run nodes for a living, not just hold them. Combined with delegate visibility, the wallet becomes a control surface for Flux infrastructure: see your delegates, see your fleet, start them all, sign as needed.
Swap UX gets a max button
Outside the operator surface, the swap screen finally gains a max button. Tap it and the swap form fills with the maximum amount the wallet can route given current balances, network fees, and the active route. It is the single feature the swap screen was asked for most often after launch, and v1.31.0 ships it with the path-aware rounding that keeps the resulting transaction valid — not just "your balance minus fees", but the largest amount that survives the swap router's own constraints.
The button does not change what swaps the wallet can do. It removes the manual math users were doing in their heads, and it removes the off-by-a-satoshi failures that come from rounding wrong before submission.
Asset-switch bug fixed
The other swap change is a bug fix, and it is the kind of bug that bit a small number of users hard. When a user picked a target chain that they had never previously held an asset on, the wallet had not always generated the derivation path for that chain before the swap was offered. The swap UI would show the route as valid, but submitting it failed at the last step because the target address did not yet exist.
v1.31.0 forces the path-generation step earlier in the flow. If a user picks a target chain the wallet has no path for, the path is derived first, then the route is offered. The user-visible behaviour is now consistent: every swap the UI offers is actually executable.
Background content scripts
The release also tightens SSP's background and inpage content scripts — the parts of the Chrome extension that broker messages between web pages and the wallet. Most users will never see the difference; dApp integrators may see fewer dropped messages on slow tabs and faster recovery after the browser parks an inactive page. Plumbing that does not get its own headline but quietly raises the floor on every dApp interaction the wallet handles.
For the full changelog and binaries, see the v1.31.0 release on GitHub.