BlazeSwap

The objective is straightforward: provide users on Flare-native networks with a swap protocol that genuinely fits the way those networks operate. Flare's FAssets mechanism enables wrapped versions of external assets — FXRP, FXLM, and others — to move on-chain without relying on centralized custody. BlazeSwap was built to support that from the beginning, not added as an afterthought later.

Most DEX forks treat every network as equivalent. The team behind BlazeSwap saw it differently. Songbird and Flare have distinct token dynamics, delegation frameworks, and reward cycles. The protocol was engineered to operate within those constraints rather than attempt to work around them.

That translates to native support for fAsset pairs, rFLR distribution through liquidity positions, and pool incentive programs anchored to real on-chain events — not arbitrary emission timetables.

BlazeSwap's foundation is an AMM — automated market maker — based on the constant-product formula. That's the same core math as Uniswap v2, which has been running since 2020 and ranks among the most thoroughly tested AMM architectures in DeFi.

The distinction lies in the layer built on top. The BlazeSwap platform adds reward routing logic tailored to Flare's token distribution model. When the Flare network distributes rFLR (reward FLR), the protocol captures those distributions on behalf of liquidity providers and routes them proportionally. The October 2024 rFLR emissions program on Flare was the first large-scale activation of this mechanism.

Pool contracts are deployed on both Flare mainnet and Songbird. Liquidity providers interact with the same interface across both networks, with the routing layer managing chain-specific differences in the background. The frontend connects via WalletConnect and supports any EVM-compatible wallet.

Smart contract source is available on GitHub. Independent audits have been completed; references are linked in the help section.

Liquidity is the difficult part of any DEX launch. Without it, swaps fail or deliver poor rates. The BlazeSwap protocol addresses this through structured incentive programs rather than unsustainable token inflation.

The FAssets incentive programs — including the December 2024 Songbird campaign and the April 2025 USDT0/USDT program — were designed to draw liquidity toward pairs that matter for Flare's broader financial infrastructure. These aren't arbitrary farming opportunities. Each program corresponds to a genuine liquidity gap identified through on-chain data.

The FXRP incentive program launched in October 2025 extended this strategy to Flare's flagship fAsset. At its peak, total value locked across BlazeSwap pools exceeded several million dollars — significant for a network-native protocol running on chains with smaller total TVL than Ethereum mainnet.

The protocol does not take a portion of emissions or incentive budgets. Fee revenue derives solely from swap fees, divided between liquidity providers and the protocol treasury.

The BlazeSwap team is lean. That's a deliberate choice. A compact group of developers with deep knowledge of Flare's architecture delivers more value than a large team working from generic DeFi templates.

Core contributors include protocol engineers who have been active on Songbird since the network's early testnet phase, frontend developers experienced with Svelte-based DeFi interfaces, and a contracts team that has maintained the AMM since the initial Flare mainnet deployment.

The team operates pseudonymously — standard practice among DeFi protocol developers. What matters is the code, the audit results, and the track record of delivering on announced programs. Since launch, every incentive program announced by BlazeSwap has shipped on schedule. The March 2026 rFLR distribution was the last in that series, completing a cycle that ran from October 2024 through Q1 2026.

Governance is minimal by design. Protocol parameters can be updated by a multisig with a defined timelock. No single key can drain funds or alter fee structures without a multi-party approval process.

Flare and Songbird are the two networks BlazeSwap operates on. Songbird serves as a canary network — new features go live there first, often months before Flare mainnet deployment. This provides the team with real-world data from production conditions before updating the primary protocol.

Flare's FAssets system is, as of 2026, one of the few functioning cross-chain asset bridges that doesn't rely on wrapped tokens controlled by a centralized party. FXRP brings XRP on-chain with cryptographic attestation rather than custodial trust. That's a meaningful technical distinction. BlazeSwap is one of the primary venues for FXRP liquidity on-chain.

The team is monitoring Flare's roadmap for FXLM and other fAsset expansions. Pool support will follow as those assets reach sufficient liquidity thresholds to make trading viable. You can track current pool status and new announcements on the main app.

The rFLR emissions cycle concluded as of March 2026. That was always the plan — a time-limited program to bootstrap liquidity, not a permanent subsidy. The protocol now operates on swap fees alone, which is the sustainable foundation for any AMM.

Future development priorities include improved routing for multi-hop swaps across fAsset pairs, potential integration with Flare's native FTSO price feeds for on-chain oracle data in limit-order functionality, and continued Songbird testing of V2 pool contracts.

Nothing speculative gets deployed without running on Songbird first. That's a standing commitment from the team, not merely a preference. If you have questions about the roadmap or want to understand how specific features work, the help page covers the protocol in detail.