Principal is not yield
hpFLR principal, validator rewards, AMM reserves, swap fees, delegation rewards, and external pool incentives have separate accounting.
Flare network
Flare-native financial infrastructure
Stake with hpFLR, swap tokens, provide liquidity and help shape the platform through governance. Explore each service below to see how it works and get started.
Public on-chainFlare mainnetProduction, chain 14
hpFLRPrincipal and rewards accounted separately
Module availabilityShown for Flare mainnet
Protocol model
Keep your staking token liquid, earn rewards and track your positions on chain.
hpFLR principal, validator rewards, AMM reserves, swap fees, delegation rewards, and external pool incentives have separate accounting.
All actions in the current release are public transactions. Users can independently verify contract calls, balances, accounting, and outcomes on the official network explorer.
FTSOv2 references constrain protected swaps. Missing, stale, malformed, or divergent mandatory data stops the affected execution.
Approved pool deployers choose, fund, disclose, and maintain their own optional reward tokens and stream periods. Forge does not issue or guarantee them.
Platform capabilities
Choose a service to get started, or expand a card to learn how it works.
Deposit native FLR one-for-one for hpFLR, retain a transferable principal receipt, enter a FIFO redemption queue, and account for validator rewards separately from principal.
The Vault receives native FLR and mints the immutable, fee-free hpFLR token. Operations may release eligible reserve only to the configured staking destination. Pending stake, confirmed stake, returned stake, liquid reserve, recognized loss, and reward liabilities are accounted as distinct states.
The allocation panel reports the strategy enabled by the selected Vault. Delegation lots and self-bonds are accounted separately. A future validator self-bond would have a 60-day term; its size and timing are not fixed. Other stakeable funds may enter 14-day delegation lots with flexible sizes and start dates. Existing lots retain their original type. At maturity, returned principal funds FIFO exits before any new bond or delegation. A lot maturity is a liquidity opportunity, not a redemption deadline.
Redemptions escrow hpFLR in a one-way FIFO queue. Claims become available only as the Vault funds queue positions; the corresponding hpFLR is burned on payment. Validator rewards are recognized from measured native balance changes and distributed through reproducible historical ownership rather than increasing the hpFLR exchange rate.
P-chain custody, validator operation, and the stake mirror are explicit operational trust boundaries. Authorized root publishers submit off-chain reward allocations; claims verify those published roots on chain. Current liquid, pending, confirmed, and - when enabled - parked and bonded allocation values are read directly from the configured deployment.
Compare received tokens, pool fees and network gas across supported markets. Review the price checks available for your trade.
Flare routes are built from indexed pools across supported venues. Quotes compare executable output and estimated gas, and identify each pool, token transition, fee and minimum received. Price checks and token transfer deductions are shown where applicable.
The executors accept typed venues rather than arbitrary call targets and enforce the signed recipient, amount limits and deadline. Forge protected routes and configured Forge pairs enforce their oracle guards on chain. External routes enforce signed output minimums; supported FTSO reference checks run before submission and do not cover every asset or pool.
Missing required data, excessive deviation, expired quotes, broken paths or insufficient executable liquidity stop the affected transaction path. The affected status explains the guard only when it triggers; a failed preflight submits no transaction.
Supply assets to stable or volatile pools, receive LP ownership, and optionally deposit that ownership into vaults that account for historical fees and eligible reward streams.
Liquidity minting and burning are proportional to reserves after permanently locked initialization liquidity. Stable pools normalize decimals and enforce a minimum usable invariant. Removal honors user minimums and permits cannot be invalidated merely by a front-run that consumes the same valid approval.
Swap fees are separated from reserves. LP vaults harvest accrued ownership before minting new shares, preserving historical claims for existing holders. Rewards arriving with zero supply are queued, and unelapsed streams are re-queued when the last staker exits.
LPs bear price movement, price impact, impermanent loss, asset-contract behavior, and market-liquidity risk. FTSOv2 guards constrain configured execution deviation; they are not insurance, a price guarantee, or a promise that liquidity can always be removed at the deposited economic value.
Stake MANA to grow your voting power, vote on proposals and direct pool weights.
Each MANA deposit creates a transferable NFT receipt. Its voting power grows linearly from 1× to 4× over 365 days and stays at 4× thereafter. Transferring a receipt preserves its age. Redeeming burns the receipt and returns its MANA, with no fixed lock period. Each additional deposit starts a new receipt at 1×. Proposals use historical voting snapshots so a transferred receipt cannot count twice in the same vote.
A proposal must reach the required state and execute with the correct description hash. Governance can exercise only functions exposed by governed contracts and remains subject to invariant checks, hard parameter caps, ownership transitions, and applicable timelocks.
Stake eligible LP positions for pool fees and, when offered, a pool-specific external reward token supplied and maintained by that pool’s approved deployer.
Gauge creation is restricted. Each gauge may be assigned one approved incentive deployer, and only that address can create and maintain the gauge’s external rewarder. LaunchPad-approved projects receive the assignment for their own pool.
The deployer approves the exact reward amount and funds the rewarder atomically with its chosen positive duration. The resulting rate must be nonzero. Revocation blocks new streams but cannot erase already funded liabilities.
Token behavior, value, disclosures, funding continuity, renewal, and legal obligations belong to the deployer. Reward-token failure is isolated from LP principal so an optional incentive cannot prevent principal withdrawal.
Coordinate bounded project funding, price formation, pool creation, liquidity ownership, and the handoff of a project-managed incentive program.
A project defines its paired asset, contribution window, funding target, minimum fill, curve type, and approved incentive assets. LaunchManager has narrowly scoped pair-creation permission and processes active launches in bounded rotating batches.
Successful funding creates liquidity under canonical pair identity and assigns resulting ownership pro rata. Rounding dust is assigned rather than becoming ownerless. Consumed accounting is cleared and unused token allowances are revoked.
An individual launch that cannot transition is deferred without blocking unrelated projects. Cancellation and completion loops are bounded, and a cap on distinct incentive tokens prevents an attacker from making finalization unexecutable.
Manage your pool's incentives, inspect its WFLR delegation and track harvested rewards.
The registry restricts eligible provider identities and the delegation manager applies bounded weights. Removing a provider also clears its lifecycle state, preventing obsolete configuration from remaining silently active.
The pair authorizes the manager through Flare’s claim-executor mechanism. A keeper supplies canonical reward proofs; the manager measures the WFLR actually received and forwards that amount to the configured distributor and LP vault.
Pool delegation yield depends on provider performance, rewards made available by Flare and successful reward harvesting.
Wrap and send native tokens, delegate to FTSO providers, claim network rewards, participate in foundation votes, and manage your personal validator stakes.
Manage your wallet →The official Flare transaction SDK resolves system contracts from Flare's registry. Transaction signatures remain in your wallet.
FTSO delegation assigns wrapped-token vote power without moving the tokens. Foundation voting uses the proposal's historical governance snapshot. Validator staking moves native tokens onto the P-chain and locks them for the selected term; it is not hpFLR minting.
Once native stake is released, transfer the available balance from P to C. Exported funds awaiting import are displayed separately, with recovery actions to complete the destination import without exporting again.
Compare swap routes, pool fees and estimated gas on Flare mainnet.
Fresh FTSO feeds are checked for FLR/WFLR and configured stablecoins in the selected route, even when the other token has no feed. A cross-asset price floor applies when both swap endpoints have feeds. The Forge hpFLR/WFLR pair also has an on-chain price guard.
Forge direct route
Balance: -
Balance: -
Choose a provider to view its staking token, rewards and redemption queue.
Mint hpFLR with C2FLR, provide liquidity on Forge, or redeem through the on-chain FIFO queue.
Your C2FLR
Your hpFLR
Still owed / waiting for liquidity
Redemption principal ready to claim
Forge liquidity paired at launch with equal hpFLR and WFLR deposits. LPs receive pool fees. Eligible LP vault shares also participate in the vault's WFLR delegation reward stream.
hpFLR reserve
WFLR reserve
Reading pool reserves from Flare mainnet…
Checking your reward claim status…
View rewards and claim optionsReceive one hpFLR for each native token deposited. Track pooled deposits and validator stakes below.
Queue allowance: -
Redeem 1 hpFLR for 1 C2FLR. Earlier requests are funded first, so your redemption may be paid in parts. Any unpaid amount remains owed in the queue until liquidity is available.
No redemption fee. Wallet network gas is paid separately for approval, joining the queue and manual claims. Queuing moves your hpFLR into escrow; it does not pay you immediately and cannot be cancelled.
Connect your wallet to view your redemption requests.
Claiming the available amount does not cancel the rest. Waiting amounts retain their FIFO priority and become claimable as liquidity returns. Staking maturity is not a guaranteed payout date.
Opt in to have funded redemptions delivered to this wallet. Actual network gas is deducted from each successful payout, within your limits. No protocol fee. Failed attempts cost the service, not your principal. This consent is separate from reward delivery. Setup requires wallet transactions.
Refresh settings to view your funded positions.
Manual claims remain available for the full allocated amount, with wallet gas paid separately. Partial payouts leave unfunded principal in its original FIFO position.
Liquid reserve
-
Vault native balance
-
Liabilities
-
Recognized rewards
-
Pending validator stake
-
Current mirrored stake
-
Next staking period end
-
Principal unlock timing. Reward availability is shown separately below.
Active allocation excludes matured lots and is displayed only when the unexpired confirmed lot inventory matches the canonical stake mirror.
Reserved for FIFO exits
-
Eligible for a new lot
-
Active parked stake
-
Parked / awaiting mirror
-
Active bonded stake
-
Bonded / awaiting mirror
-
Parking term
-
Bond term
-
Parking freezes
-
Next bond roll
-
A P-chain delegation cannot be withdrawn before its recorded end. A redemption can be requested at any time and keeps its immutable FIFO position. Liquid reserve funds the oldest exits immediately. As each parked or bonded lot matures, automation returns its exact principal to the Vault and funds queued exits before considering another delegation. hpFLR is burned only when funded native FLR is paid out.
These accounting entries can include completed stake that has not been reconciled. They are excluded from the active allocation above.
Assets recorded by Vault: -
Recorded parked stake: -
Recorded bonded stake: -
Matured lots awaiting reconciliation: -
Direct hpFLR holders need no registration. Registered LP tokens and LP vault shares can attribute rewards to their underlying holders through the epoch calculator. Third-party reward collection requires approval and holder authorization.
Validator reward status
Checking rewards…
Your reward claim availability
Checking schedule…
MIRROR and validator rewards add to one balance as epochs are processed. Claim the full balance in one wallet transaction.
Connect your wallet to load published on-chain reward epochs.
Opt in to automatic delivery of your cumulative hpFLR holder rewards, including MIRROR and stake-lot allocations, or your personal Flare network rewards. Manual claims remain available.
If you turn it on, a service can submit claims for you. It advances transaction gas and deducts the actual allowed gas cost from a successful reward; there is no service fee. Failed attempts cost you nothing. You choose the maximum gas deduction, minimum amount you receive, and expiry. Setup requires wallet approvals. You can turn it off later.
Check my setup to see whether this optional service is authorized.
Check my setup first, then choose the limits you accept. These are your maximums, not fixed charges.
Invest hpFLR in a position that earns independently of existing shareholders. Rewards compound into your position. After settlement it converts to common wrapper shares for compatible strategies. You can cancel your position and keep rights to delayed rewards.
Wrap common shares into transferable normalized yield shares, or unwrap them back. Wrapping does not convert an unsettled position.
Refresh to read your positions from the configured wrapper.
Apply for reward collection by a protocol or strategy that holds hpFLR. Each configuration requires admin approval and holder authorization. Approval authority can later move to governance. Manual holder claims remain available.
Vaults, lending markets and yield strategies apply through this shared review process. Each integration must show how it preserves contributors' earned rewards through deposits, withdrawals and transfers. hpFLR principal remains 1:1, with rewards accounted separately. Share-price, liquidation and yield-maturity behavior require verification for the proposed integration.
Your submitted use case, addresses and review notes are public and permanent on-chain. Do not include secrets or private contact information.
Choose who receives the rewards and the maximum gas deduction. You receive rewards minus the gas deduction, in the selected asset. The admin must approve the application, and the holder must authorize it. Failed delivery leaves rewards unclaimed; principal is never charged.
Register the recipient and claimant from the holder contract. The application details provide exact calls for its governance or contract wallet. An ERC-1271 holder can also authorize by signature; the holder contract verifies who may sign.
Connect a wallet and load an application to check this deployment. Gas is deducted from rewards only when you select and authorize that option; otherwise the service pays it.
Provide liquidity to earn swap fees, delegation yield, and any explicitly configured reward funded by that pool's approved deployer.
Wallet balance: connect wallet
Wallet balance: connect wallet
Pool: not yet detected
Enter either token amount. The other is calculated automatically from the pool's reserve ratio. Minimum amounts allow 1% movement.
Connect wallet to see required approvals and transactions.
Balance: -
Connect wallet to view positions.
Your stake is a transferable NFT receipt. Its voting power grows from 1× to 4× over 365 days. Redeem whenever you choose - there is no fixed lock term.
Each deposit creates a transferable NFT receipt for your MANA. Every new receipt starts at 1× voting power.
Connect your wallet to view your MANA.
Voting power belongs to the position, not its original wallet. Transferring the NFT transfers its MANA claim, age, and voting power. Redeeming returns that position’s MANA and burns its NFT; its voting power ends. Other positions keep their age.
Governance proposals use historical voting snapshots, so moving a receipt between wallets cannot count its power twice on the same proposal. Fees already earned remain claimable by the wallet that earned them. MANA is a governance token, not an incentive payout.
-
Connect your wallet to view receipts.
Approve trading pools and infrastructure-provider LSTs. MANA voting receipts carry the voting power; approved provider proposals deploy their own branded staking and rewards contracts.
Total vote power
-
From veMANA
-
From staked MANA
-
Stake multiplier
-
Vote For or Against each active proposal. Passed proposals can be executed by anyone.
Loading proposals…
Requires veMANA or staked MANA above the proposal threshold.
Launch a verified provider LST
Choose an eligible receipt to automate existing-pool weight votes. The Auto-Voter does not vote on new-pool proposals.
AVM total VP
-
Status
-
-
Voting delay
-
Voting period
-
Quorum
-
Explore swap fees, WFLR delegation yield and pool-funded rewards.
Forge pool swap fees belong entirely to LP holders and are accounted separately from pool reserves. Claim them through your LP position or vault. Routing through external platforms adds no Forge fee; those venues apply their own pool fees.
Fee rate
Set per pool
LP share
100%
→ Add liquidity in the Liquidity tab.
An approved pool deployer may supply its own reward token to its own approved pool. Forge does not issue, fund, custody, endorse, guarantee, or maintain that token or program.
Funding source
Pool deployer
Availability, token behavior, reward rate, continuation, disclosures, and regulatory obligations remain the supplying deployer's responsibility.
Fund an incentive program with your chosen reward token and duration.
Manage pool incentivesFlare's network pays WFLR to anyone who delegates to an FTSO data provider. Forge pools that hold WFLR delegate automatically. A keeper bot harvests those rewards and streams them to vault depositors - 100% to LPs, 0% to the protocol.
Eligible pools
Registered WFLR pairs
fXRP / WFLR
USDT0 / WFLR
Reward token
WFLR
Protocol cut
0%
Deposit LP tokens to earn WFLR delegation rewards, distributed over seven days after each harvest.
Total LP Deposited
across all vaults
WFLR / week
active reward streams
Your Total Earned
claimable WFLR
Configured Vaults
ERC4626 · 7-day stream
Connect wallet or loading…
Rewards stream per-second over 7 days after each keeper harvest. fLP tokens are transferable - buyers inherit the live WFLR yield stream.
Launch an infrastructure-backed LST or fund a new liquidity project.
Download the provider registration & operating guide
hpFLR is the initial infrastructure LST. Propose a provider's own branded version here. Its native principal mints and redeems 1:1 through an independent FIFO queue. The provider manages its own finances, staking and rewards distribution; the platform does not fund or guarantee its rewards. A new token needs actual liquidity before swaps are executable.
Connect your entity, delegation, submit, submit-signatures or signing-policy wallet. Your registered validators are read from Flare's EntityManager.
Loading launch pools…
Pool-owned FTSO delegation, harvest accounting and deployer-funded incentives in one place.
View the selected pool's WFLR delegation and provider split.
Registered pairs
-
WFLR held by registered pools
-
Governance-created WFLR pairs are registered automatically. This recovery control registers an existing pair with the protocol's primary provider.
Track WFLR harvested for LP vault depositors. Harvested rewards are streamed through the pool's LP vault.
First configured vault
-
Second configured vault
-
Your wallet
Manage tokens, delegate to FTSO providers, stake with validators and vote on Flare proposals.
Delegate your wrapped-token vote power without transferring your tokens. Updating the split replaces your existing personal FTSO delegations.
Claim your FTSO delegation and validator staking rewards.
hpFLR claims first deliver native FLR to your wallet, then mint the confirmed reward amount through the hpFLR Vault. You confirm two transactions. If the mint cannot finish, the claimed FLR stays in your wallet.
Choose an address to vote on your behalf. Voting eligibility is determined at each proposal's snapshot.
Transfer native tokens to the P-chain and stake with a validator. Funds stay locked until your selected end time, then can be transferred back to your C-chain wallet. Each transfer requires an export and an import.
The wallet handles C-chain RPC. P-chain staking needs a separate node connection made directly by your browser.
Your wallet may request a message signature to derive your public P-chain address. No private key is requested or stored.