The Forge

Pool ownership

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.

Fees and vaults

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.

Risk

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.

Voting power

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.

Execution

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.

Authorization

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.

Funding

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.

Responsibility

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.

Lifecycle

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.

Settlement

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.

Failure isolation

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.

Delegation

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.

Harvest

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.

Reward availability

Pool delegation yield depends on provider performance, rewards made available by Flare and successful reward harvesting.

Your wallet signs

The official Flare transaction SDK resolves system contracts from Flare's registry. Transaction signatures remain in your wallet.

Three distinct actions

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.

Return and recovery

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.