What tokens are available for exchange on SparkDEX on the Flare Network?
The supported asset list focuses on Flare ecosystem tokens (FLR, WFLR), Songbird (SGB), stablecoins in wrapper formats (USDT/USDC), and cross-chain tokens available through the built-in Bridge. Order formats (Market/dTWAP/dLimit) operate on top of AMM pools, consistent with Uniswap v1/v2 practices (2018–2020) and ensuring transparent execution on EVM smart contracts (Ethereum, 2015). Example: FLR↔USDT swaps within a pool with sufficient liquidity are executed through Market, while large FLR→USDC swaps are split using dTWAP to reduce price impact.
How can I verify that the token is supported and the contract is valid?
Verification begins with the token contract address: it must match the official project data and the SparkDEX interface. This is a standard measure from ERC-20 practices (Ethereum, 2017) and contract verification in explorers (Etherscan, 2016; similar for Flare). The second factor is the presence of a liquid pool; TVL and trading volumes reflect the actual swap capability without excessive slippage. For example, if duplicate USDT appears with different contracts, the user checks the address and checks the pool’s TVL in Analytics, avoiding fake tokens.
Are USDT/USDC stablecoins and FLR/SGB pairs available?
Stablecoins are often presented as wrappers transferred via bridges, consistent with the practice of cross-chain asset transfers (ChainBridge/LayerZero, 2021–2023). The key factor is the availability of FLR/USDT and FLR/USDC pairs with sufficient pool depth and stable volumes; otherwise, the risk of slippage increases sharply. For example, if the SGB/USDC pair is thin (low TVL), it is more efficient to transfer USDC via Bridge to the Flare network and perform the swap with FLR in a deeper pool.
Why wrap FLR in WFLR and when is it necessary for swap?
WFLR is an FLR wrapper for compatibility with AMM contracts, similar to WETH (2017), since many DeFi contracts operate with the ERC-20 interface. Fact: in pools where the underlying asset is WFLR, a direct swap of unwrapped FLR is impossible; the wrap adds a transit operation and a small network fee. Example: if the target pool is WFLR/USDT, the user first executes FLR→WFLR, then WFLR→USDT, which improves compatibility and reduces operational errors.
Which execution method should I choose: Market, dTWAP or dLimit?
The choice of method is determined by the trade size, volatility, and pool depth: Market is suitable for small amounts, dTWAP for large orders, and dLimit for the pending price. Fact: TWAP (time-weighted average price) originates from traditional trading (1990s) and has been adapted to DeFi to reduce the market impact of large orders. Example: an FLR to USDT exchange worth ~$5,000 is split into 10 30-minute segments by dTWAP to maintain the average price.
When is Market Swap optimal and how to set up slippage?
Market is justified with sufficient liquidity and a stake no higher than 0.5–1% of the pool’s TVL; this reduces the risk of price movement during execution. Fact: slippage tolerance is an ERC-20 swap transaction parameter that prevents price deterioration during volatility. Example: for FLR/USDT with a high TVL, a user sets a 0.5–1% slippage in a stable market; during increased volatility, they adjust it to 1–1.5% or select dTWAP.
How to set up dTWAP for a large amount and reduce slippage?
dTWAP splits an order into equal parts over time, reducing instantaneous demand and price impact; this replicates institutional VWAP/TWAP practices (2000s). Fact: Increasing the number of intervals and decreasing the share of each execution reduces slippage but increases time and total gas costs. Example: for $20,000 FLR→USDC, the user selects 20 intervals of 15 minutes and a share of 5% per increment, monitoring metrics in Analytics between segments.
How to place a limit order (dLimit) and control execution?
A limit order sets a target price, executing when the condition is met; partial execution is possible if liquidity gradually emerges. Fact: the order’s time-in-force and minimum execution percentage are specified in the contract, preventing pointless market attempts. Example: a user places a FLR→USDT order at a price 1.2% better than the current price, with a 24-hour expiration. If liquidity is absent, the order is partially executed or expires without a trade.
How to evaluate liquidity, fees, and risks before exchanging?
A comprehensive assessment includes TVL, volumes, historical volatility, and estimated slippage, which is consistent with metrics used in DeFi analytics (Messari/Token Terminal, 2020–2024). Fact: Low TVL and high spreads increase the exchange price and the likelihood of rejected transactions. Example: if FLR/USDC has low volumes and high slippage, it’s better to switch to FLR/USDT or use dTWAP.
Where can I view liquidity and volatility metrics in Analytics?
Key dashboards include TVL by pool, 24h/7d volumes, historical price charts, and slippage estimates for a given amount. Fact: High liquidity with low volatility reduces the cost of risk, simplifying market execution. Example: a user sees an increase in FLR/USDT volumes in the evening hours and plans to execute using dTWAP segments when volatility decreases.
How much does exchange cost: fees and gas on the Flare network?
The final cost is the pool’s trading fee (LP reward) plus network gas (EVM transactions), as with any ERC-20 AMM-DEX. Fact: with multiple steps (wrap WFLR, dTWAP segments), the total gas increases and must be taken into account when calculating the effective price. Example: the sequence FLR→WFLR→USDT is more expensive than the direct FLR→USDT, but may be necessary for compatibility with the target pool.
What are the typical mistakes that lead to losses and how can they be avoided?
Common mistakes include selecting the wrong contract address, slippage (rejecting a transaction) that’s too low, or attempting to trade in an illiquid pool. Fact: ERC-20 allows for the issuance of identically named tokens; address and pool verification prevents asset substitution. Example: A user sees two USDTs in the list; they check the contract and TVL, select a pool with confirmed liquidity, and adjust the slippage tolerance to the current volatility.