< Back to Newsroom

Claim Flux Parallel Assets from SSP Wallet

·3 min read·By SSP Editorial Team
Navy SSP cover with coins, database, zap and shield icons announcing Flux Parallel Assets claim in SSP

On February 19, 2024, SSP Wallet v1.2.0 integrates Fusion directly into the wallet UI. Flux node operators can now claim Flux Parallel Assets straight from the Nodes section: SSP gathers the rewards across every chain they live on, swaps them to the Flux main chain, and deposits the result to the operator's Flux address — without a single manual cross-chain hop.

TL;DR

  • SSP Wallet v1.2.0 lets node operators claim Flux Parallel Assets (PA) inside the wallet.
  • The new action lives in the Nodes section and runs in a single confirmation.
  • SSP automatically claims PAs on every supported chain they exist on.
  • Each batch is swapped to the Flux main chain via Fusion before payout.
  • The final reward is deposited to the user's Flux address.

What Parallel Assets are

Flux runs as a multi-chain network: the same FLUX asset is issued on several chains, and node operators are rewarded simultaneously on each of them. These cross-chain rewards are known as Parallel Assets, or PAs. Historically, collecting them was a bookkeeping exercise — log in to each chain, claim the relevant PA, bridge or swap it, then consolidate everything on the Flux main chain. Each hop carried its own fees, its own wallet, and its own waiting time. From v1.2.0, SSP Wallet collapses all of that into one signed action.

How the in-SSP claim flow works

Open SSP Wallet and navigate to the Nodes section. Alongside the existing node management views, v1.2.0 surfaces a claim action whenever a node has unclaimed Parallel Assets available. Choosing it kicks off the Fusion-powered pipeline end-to-end. SSP enumerates every chain on which that node has accrued a PA and prepares the claim transactions in parallel. Each claimed batch is then routed through Fusion's swap path, converting the per-chain PA into native FLUX on the Flux main chain. The consolidated reward is finally deposited to the user's Flux address inside SSP. The user signs once on the extension, co-signs once on the SSP Key on their phone, and the wallet handles the rest.

Why this matters for Flux node operators

The before-and-after is stark. Previously, claiming Parallel Assets meant juggling separate wallets per chain, paying gas in several different native assets, and manually swapping each PA back to mainline FLUX through whatever bridge or DEX was convenient. Mistakes were expensive: a typo at any step could route funds to the wrong network entirely. With v1.2.0 in place, the operator's mental model collapses to a single line — "claim my PA rewards" — and SSP performs the per-chain reads, the multi-chain signing, the swap routing, and the final deposit as one composed transaction graph. The 2-of-2 multisig posture is preserved throughout, so no individual device ever holds enough material to move funds on its own. For operators running multiple nodes, the time savings compound quickly: instead of repeating the same per-chain ritual once per node, the entire fleet's accrued PAs can be processed in one sitting.

What's next

Fusion-backed PA claims are the first real cross-chain action SSP performs on the user's behalf, and the architecture is designed to extend. Future SSP Wallet releases will broaden the catalogue of chains and assets the Nodes flow understands, and Fusion's swap layer will pick up additional routes as they ship — fiat support, contacts, and a wider asset list are all on the near roadmap. The principle, however, is fixed: any complex on-chain operation should reduce to a single approve-and-cosign for the user, with SSP and Fusion handling the bookkeeping behind the scenes. PA claims are the proof of concept; the broader catalogue of one-click cross-chain operations follows from there.

Source: SSP Wallet v1.2.0 release notes.

Share this article

Related articles