Question 1

What is Fly.trade?

Accepted Answer

Fly.trade is a liquidity aggregation and trade-execution protocol for on-chain and cross-chain asset swaps. Rather than using a single trading pool as its sole quote source, it integrates existing decentralized exchanges (DEXs) and bridge liquidity pools to find executable routes for users' selected assets and chains. This design addresses fragmented multichain liquidity: available liquidity for the same asset or trading pair may be distributed across different protocols and chains. Fly's router uses these sources to seek quotes; actual execution price, slippage, and available routes still vary with prevailing liquidity, trade size, and selected chains.

Question 2

What is the FLY token used for?

Accepted Answer

FLY is Fly.trade's protocol token. Its announcement describes it as an incentive and governance tool connecting traders, stakers, and the protocol. Under its ve(3,3)-inspired model, locking FLY yields xFLY and enables holders to vote on protocol fees, emissions, and partnership matters. Accordingly, FLY's governance utility does not apply automatically to each swap; it works through locking and voting on protocol-level parameters and incentive allocation. The announcement also describes a design for distributing fees to stakers; actual eligibility, allocation, and yield outcomes remain subject to the currently deployed protocol rules and participation status.

Question 3

How do I swap on Fly.trade?

Accepted Answer

To initiate a swap on Fly.trade, first connect a self-custody wallet, then select the source chain, destination chain, input asset, output asset, and amount. Once the interface generates an executable quote, the user must complete any required token approval in the wallet and confirm the transaction; approval lets a contract use the token up to the approved amount, while confirmation submits the specific swap operation. After confirmation, the protocol executes the on-chain or cross-chain steps along the selected route, and the destination asset is sent to the user's wallet. It is important to verify the source and destination chains, tokens, amount, quote, and wallet address before trading; results after on-chain confirmation cannot simply be treated as something the interface can unilaterally reverse.

Question 4

What does a cross-chain swap mean in practice for users?

Accepted Answer

For cross-chain swaps, Fly.trade combines bridges and their messaging layers to connect an operation on the source chain with a subsequent swap or delivery on the destination chain; users do not need to find a bridge and a destination-chain DEX separately. The protocol documentation emphasizes that this approach can complete a cross-chain trading route without first manually swapping into a stablecoin or the destination chain's native asset. A cross-chain swap is not a single instant exchange on one chain: it involves at least a source-chain transaction, cross-chain messaging or asset transfer, and destination-chain processing. The ultimately available route, delivery time, quote, and cost are affected by the selected chains, bridge and DEX liquidity, and on-chain conditions.

Question 5

What is xFLY after locking FLY?

Accepted Answer

As described in the announcement, xFLY is a participation credential obtained by locking FLY. Its purpose is to let lockers take part in governance votes related to protocol fees, emissions, and partnership matters; the announcement also associates it with staking, voting, and related incentive arrangements. FLY and xFLY should be distinguished here: FLY is the base protocol token, while xFLY is the form received after locking FLY for governance participation. Locking does not guarantee a fixed return; voting power, possible incentives, and fee distributions all depend on the then-current protocol rules and whether the user meets the relevant conditions.

Question 6

How are FLY's TGE and the Magpie Protocol name related?

Accepted Answer

FLY's token generation event (TGE) launched on Sonic on June 6, 2025, at 13:00 UTC. This event marks the public launch of FLY as Fly.trade's native token; it does not mean that Fly.trade itself first began offering cross-chain swap services on that date. The announcement also states that Fly.trade was formerly known as Magpie Protocol. Therefore, earlier project materials, app links, or historical reporting may use the Magpie Protocol name; this reflects the project's naming history and should not be mistaken for a separate unrelated protocol.

Question 7

How does Fly.trade address fragmented multichain liquidity?

Accepted Answer

Fly.trade's same-chain routing aggregates liquidity from multiple DEXs, while cross-chain routing also uses bridge liquidity pools. Pooling more available sources aims to reduce the effects of liquidity fragmentation on market depth, slippage, and quotes, while allowing the router to select routes across available sources. This is a routing and liquidity-integration mechanism; it does not mean every trade receives the same or a fixed lowest cost. Large orders, insufficient liquidity, bridge status, and on-chain gas can all change a particular trade's actual cost and execution result.

Question 8

Why do I need both approval and confirmation for a swap?

Accepted Answer

When using Fly.trade, users must complete two distinct actions before a quote is executed: token approval and transaction confirmation. Approval lets the relevant contract transfer input tokens within a specified allowance; transaction confirmation signs and broadcasts the particular same-chain or cross-chain swap request. They are separate because control of a token balance and an instruction for a particular trade are not the same permission. Users should check the approval recipient and amount in their wallet, and review the chain, input and output assets, and amount when confirming the transaction; the official website's listed flow also identifies “approve and confirm quote” as required steps after selecting trade terms.

Question 9

Why can liquidity aggregation affect quotes and slippage?

Accepted Answer

Fly.trade's aggregation model may improve quotes and slippage because the router can use liquidity from multiple DEXs and bridges instead of executing against only one pool. When market depth increases, an order of the same size may have less price impact on a single pool, creating an opportunity for a more suitable executable route. However, “aggregation” is not a price guarantee. Slippage still depends on order size relative to available liquidity, and quotes change with market and on-chain conditions; between the quote shown before confirmation and final execution terms, the specific trading rules of the selected route still apply.

Question 10

What role does the bridge messaging layer play in Fly.trade cross-chain swaps?

Accepted Answer

Fly.trade's cross-chain design incorporates a bridge's messaging layer into the execution route, enabling an intent on the source chain to trigger subsequent operations on the destination chain. Compared with a user manually completing the multistep process of “bridge first, find a DEX, then swap,” this integration leaves route selection and step coordination to the protocol. The messaging layer serves a cross-chain coordination role; it does not eliminate dependencies on the underlying bridge, destination-chain execution, or liquidity sources. If the availability or state of any link changes, executable routes and the actual user experience may also differ.

Question 11

What matters can xFLY governance voting affect?

Accepted Answer

Fly.trade's announcement links xFLY governance rights to protocol fees, emissions, and partnership matters. Fees concern how fees generated by the protocol are handled, emissions concern the direction of incentive-token allocation, and partnership matters involve collaboration arrangements between the protocol and external projects; these are protocol-level rather than individual-swap choices. Locking FLY does not give an individual automatic control over every matter; it provides eligibility to participate in voting under the protocol's governance mechanism. Final outcomes typically depend on voting rules, participation, and governance proposals that take effect.

Question 12

How should Fly.trade's swap mechanism be distinguished from FLY's governance mechanism?

Accepted Answer

Fly.trade's core relationship can be summarized as follows: a user enters a swap request, the router selects a same-chain or cross-chain execution route from DEX and bridge liquidity, the wallet completes approval and confirmation, and assets are then delivered to the user's wallet along that route. FLY and xFLY sit in the protocol's incentive and governance layer, rather than being required gas assets for every trade. Accordingly, “how a swap executes” and “how FLY participates in protocol governance” should be assessed separately. The former mainly depends on assets, chains, liquidity, bridges, and wallet confirmation; the latter depends on FLY locking, xFLY, and the governance and incentive rules in effect at the time.

Fly.trade (FLY) Price

Price of Fly.trade (FLY) Today in USD