Wallet Management
ZelCore, SSP Wallet, collateral management, address types, and security best practices.
Wallet Management β ZelCore, SSP & More
Managing your FLUX wallet is fundamental to operating nodes and interacting with the Flux ecosystem. This guide covers the supported wallets, collateral management, address types, and security best practices.
Supported Wallets
| Wallet | Type | Features | Best For |
|---|---|---|---|
| ZelCore | Desktop / Mobile | Multi-coin, node management, d2FA, Fusion app | Most node operators |
| SSP Wallet | Desktop / Mobile | Modern UI, FluxNode management, ArcaneOS tokens | New users, ArcaneOS setups |
| MetaMask | Browser extension | Ethereum-compatible Flux interactions | DeFi users, Flux ERC-20 tokens |
| WalletConnect | Protocol | Connect any WalletConnect-compatible wallet | Mobile wallet users |
Flux Address Types
- β’t1 addresses: Transparent addresses starting with "t1". Standard Flux addresses for most transactions. Used for single-key node collateral.
- β’t3 addresses: Pay-to-Script-Hash addresses starting with "t3". Used for multi-signature setups and P2SH delegate node operations.
- β’z-addresses: Shielded (private) addresses. Inherited from the Zcash codebase. Transactions are encrypted on-chain.
Collateral Management
To operate a Flux node, you must lock collateral in a single UTXO (Unspent Transaction Output):
| Tier | Collateral (FLUX) | Confirmations Required |
|---|---|---|
| Cumulus | 1,000 | 100 (~3.5 hours) |
| Nimbus | 12,500 | 100 (~3.5 hours) |
| Stratus | 40,000 | 100 (~3.5 hours) |
The collateral must be in a SINGLE transaction to a SINGLE address. Do not send multiple small amounts β they must arrive as one UTXO. If you already have FLUX in your wallet, consolidate it into one transaction of the exact collateral amount.
- 1
Create a receiving address
In ZelCore or SSP Wallet, create a new Flux address specifically for your node collateral.
- 2
Send the exact amount
Send exactly 1,000 / 12,500 / 40,000 FLUX in a single transaction to this address.
- 3
Wait for confirmations
100 confirmations (~3.5 hours at 2 min/block) are required before you can start your node.
- 4
Get the collateral output
In ZelCore: go to Flux > Tools > FluxNode > Get Outputs. This gives you the TX hash and output index needed for node setup.
Security Best Practices
- β’Seed phrase backup: Write down your 24-word seed phrase on paper and store it in a secure physical location. Never digitize it.
- β’d2FA (decentralized 2FA): ZelCore supports d2FA which adds a second layer of authentication using a separate device.
- β’Separate wallets: Use a dedicated wallet for node collateral, separate from daily spending.
- β’Test transactions: Before sending large amounts, send a small test transaction to verify the address.
- β’Never share keys: No legitimate Flux team member or support person will ever ask for your private key or seed phrase.
Removing a Node & Unlocking Collateral
To stop running a node and recover your collateral:
- β’Simply send your collateral to another address (including back to yourself). This automatically deregisters the node.
- β’The node will go offline within 1β2 confirmation cycles after the collateral is moved.
- β’There is no waiting period or penalty for removing a node β collateral is fully liquid once moved.
Other articles in Flux Ecosystem
FluxCloud Deployment Guide
Deploy apps via Docker or Git CI/CD, manage instances, marketplace templates, and pricing model.
FluxEdge GPU Computing
Decentralized GPU marketplace β rent H100/A100 GPUs for AI, rendering, and compute workloads.
FluxCore Desktop App
Turn your PC into a FluxEdge compute provider. Install, benchmark, and start earning FLUX.
Fusion & Cross-Chain Bridge
Bridge FLUX across 8+ blockchains, claim parallel mining rewards, and understand supply lock mechanics.
Network Architecture
How Flux works under the hood β blockchain, FluxOS, FDM domain management, Syncthing, and the API gateway.