Flare Staking

Flare staking is proof-of-stake participation on Flare's P-Chain, where you lock native, unwrapped FLR against a validator NodeID for a fixed period you choose and add validation weight to the network. Flare runs Snowman++ consensus derived from Avalanche's Snow protocols; Avalanche's consensus documentation explains that protocol family.

Delegation creates no liquid staking token: your FLR is simply locked, unlike systems that issue a liquid staking token to represent a staked position. Flare staking is separate from FTSO delegation, which uses wrapped WFLR on the C-Chain to back data providers without locking anything. Staked FLR cannot simultaneously earn WFLR-based FTSO rewards, so one token position serves one role at a time.

Flare staking works through a C-Chain-to-P-Chain export/import, not a smart-contract deposit. Hold unwrapped FLR on the C-Chain, connect a compatible wallet to the Flare Portal or use the staking CLI, and export/import the FLR to the P-Chain. Then choose a validator NodeID, amount, and permitted end time, and sign the delegation transaction.

Delegation requires at least 50,000 FLR locked for at least 14 days; validator self-bonding carries higher amount and duration requirements. FLR stays locked until your chosen expiry, and rewards accrue from validator performance and the validator's disclosed fee. After automatic unlock, move the FLR back to the C-Chain and claim rewards separately. The mechanism was formalized in Flare's Phase 2 staking rollout, and there is no slashing of delegated stake in the classic sense: underperformance mainly costs you rewards, not principal.

The two protocol-level routes are delegation and self-bonding. Delegation is what most holders do: lock 50,000+ FLR against an existing validator through the Flare Portal, keep your keys, and accept the validator's fee on rewards. Self-bonding means running your own validator for more control and no third-party fee, with higher minimums, longer commitments, and operational responsibility for uptime.

If you do not meet the delegation minimum or do not want a lock at all, FTSO delegation with WFLR on the C-Chain is the adjacent no-lock option; it is not staking and has a different reward stream. For delegation, compare a validator's disclosed fee, capacity, and operational history on an independent explorer before assigning weight.

Flare staking rewards are performance-based rather than a fixed APY: they flow from the protocol to validators for consensus work, and delegators receive a share proportional to their staked weight minus the validator's disclosed fee. The effective rate varies with validator uptime and performance, the validator's fee, and network-wide parameters, so any headline figure elsewhere is a snapshot, not a promise.

Rewards generally become claimable in batches about every two weeks and must be claimed separately after your stake unlocks; they do not auto-compound, and expired stakes do not automatically restake. Read the current rate and each validator's fee in the Flare Portal, then use Flare's DefiLlama page for broader network context.

The defining risk of Flare staking is the hard lock: there is no early exit from an active delegation, so FLR's price can move while you cannot react.

The remaining exposures are validator risk when poor performance reduces rewards; self-custody risk because you hold the signing keys and lose them means the stake is gone; protocol and smart-contract risk; operational risk in the C-Chain/P-Chain transfer steps; and market risk on FLR itself. The Phase 2 staking code received an independent security review, but no audit removes protocol risk. Native staking issues no liquid staking token, so depeg risk does not apply; a third-party liquid or custodial wrapper adds depeg and provider risk.

To start, choose delegation if you want an existing validator to run the infrastructure, or self-bonding if you can run your own validator. Set up a compatible wallet, secure your seed phrase offline, and hold unwrapped FLR: WFLR must be unwrapped before it can move to the P-Chain. Keep a small FLR buffer for transaction fees; gas documentation explains why transaction fees are separate from the amount you lock.

The practical sequence is: connect your wallet to the Flare Portal, deposit FLR into the staking account, use the export/import step to move it from C-Chain to P-Chain, choose a validator NodeID after checking its fee and track record, set your amount and end time — minimum 50,000 FLR and 14 days for delegation — and sign. Flare's staking CLI does the same job, and tooling and code live in the Flare Foundation GitHub.

Unstaking starts only at the end time you selected: there is no unstake button mid-lock, FLR unlocks automatically at expiry, nothing is instant before that point, and no support ticket changes it.

After expiry, transfer the FLR from the P-Chain back to the C-Chain and claim accumulated rewards separately; rewards do not arrive with the principal automatically. An expired stake sits unlocked and does not restake itself, so continued rewards require a new delegation. Network fees apply to the transfers and the claim, which is why the FLR buffer remains useful.