Blazeswap

The objective is straightforward: provide users on Flare-native networks with a swap protocol that genuinely fits how those networks operate. Flare's FAssets mechanism enables wrapped versions of external assets — FXRP, FXLM, and others — to exist on-chain without centralized custody. Blazeswap is engineered to support that from the very beginning, rather than treating it as a feature added later.

Most DEX forks approach every network as though it were identical. The team behind Blazeswap took a different view. Songbird and Flare have distinct token dynamics, delegation systems, and reward cycles. The protocol was constructed to operate within those realities rather than working around them.

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

Blazeswap's foundation is an AMM — automated market maker — based on the constant-product formula. This is the same underlying mathematics as Uniswap v2, which has been operating since 2020 and stands as one of the most thoroughly tested AMM designs in DeFi.

What sets it apart is 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 allocates them proportionally. The October 2024 rFLR emissions program on Flare marked the first large-scale deployment of this mechanism.

Pool contracts are deployed on both Flare mainnet and Songbird. Liquidity providers work through the same interface on 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 code is available on GitHub. Independent audits have been completed; references are linked in the help section.

Liquidity is the most difficult aspect of any DEX launch. Without it, swaps fail or return unfavorable 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 crafted to draw liquidity toward pairs that matter for Flare's broader financial infrastructure. These are not arbitrary yield 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 approach to Flare's flagship fAsset. At its peak, total value locked across Blazeswap pools surpassed several million dollars — significant for a network-native protocol operating on chains with smaller total TVL than Ethereum mainnet.

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

The Blazeswap team is lean. That is deliberate. A compact group of developers with a deep understanding of Flare's architecture delivers more value than a large team relying on generic DeFi templates.

Core contributors include protocol engineers who have been active on Songbird since the network's early testnet phase, frontend developers experienced in 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 counts is the code, the audit outcomes, and the record of delivering on announced programs. Since launch, every incentive program announced by Blazeswap has been released 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 intentionally minimal. Protocol parameters can be adjusted 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 launch there first, often months before deployment on Flare mainnet. This provides the team with real-world production data before updating the primary protocol.

Flare's FAssets system is, as of 2026, one of the few functioning cross-chain asset bridges that does not depend on wrapped tokens controlled by a centralized party. FXRP brings XRP on-chain through cryptographic attestation rather than custodial trust. That is 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 once those assets reach sufficient liquidity thresholds to make trading viable. Current pool status and new announcements can be tracked on the main app.

The rFLR emissions cycle concluded as of March 2026. That was always the intent — a time-limited program to bootstrap liquidity, not a permanent subsidy. The protocol now runs 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.

No speculative features ship without running on Songbird first. That is 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.