Blazeswap

The goal is direct: give users on Flare-native networks access to a swap protocol that actually fits how those networks work. Flare's FAssets mechanism lets wrapped versions of external assets — FXRP, FXLM, and others — move on-chain without centralized custody. Blazeswap is built to support that from day one, not bolt it on as an afterthought.

Most DEX forks treat every network as interchangeable. The team behind Blazeswap disagreed. Songbird and Flare have specific token dynamics, delegation systems, and reward cycles. The protocol was written to work within those constraints rather than around them.

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

Blazeswap's core is an AMM — automated market maker — based on the constant-product formula. That's the same underlying math as Uniswap v2, which has been running since 2020 and is one of the most battle-tested AMM designs in DeFi.

What differs is the layer on top. The Blazeswap platform adds reward routing logic specific 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 deployment 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 handling chain-specific differences behind the scenes. The frontend connects via WalletConnect and supports any EVM-compatible wallet.

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

Liquidity is the hard part of any DEX launch. Without it, swaps fail or produce bad 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 attract liquidity to pairs that matter for Flare's broader financial infrastructure. These aren't arbitrary farming opportunities. Each program corresponds to a real liquidity gap identified through on-chain data.

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

The protocol does not take a cut of emissions or incentive budgets. Fee revenue comes from swap fees only, split between liquidity providers and the protocol treasury.

The Blazeswap team is small. That's intentional. A small group of developers who understand Flare's architecture deeply is more valuable 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 with experience in Svelte-based DeFi interfaces, and a contracts team that has been maintaining the AMM since the initial Flare mainnet deployment.

The team operates pseudonymously — standard practice for 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 final one 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 change fee structures without a multi-party approval process.

Flare and Songbird are the two networks Blazeswap operates on. Songbird functions as a canary network — new features go live there first, often months before Flare mainnet deployment. This gives the team 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 entity. 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 watching Flare's roadmap for FXLM and other fAsset expansions. Pool support will follow as those assets achieve sufficient liquidity thresholds to make trading viable. You can track current pool status and any new announcements on the main app.

The rFLR emissions cycle is complete as of March 2026. That was always the plan — a time-limited program to bootstrap liquidity, not a permanent subsidy. The protocol now runs on swap fees alone, which is the sustainable baseline 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 shipped without running on Songbird first. That's a standing commitment from the team, not 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.