Traderjoexyz swap fees across pools and routes

Traderjoexyz swap fees vary with the pools that a route uses, so the quoted output matters alongside the fee rate. Trader Joe now operates under the LFJ brand. Its Swap page adds no platform fee, although pool charges and network gas remain payable. Liquidity Book pools combine base and variable fees, while Joe V1 follows a different fee rule. Compare the same input amount and output token, then account for authorization costs and the minimum output that the transaction allows.

Quoted output and the amount that reaches the wallet

A swap quote estimates the output that a selected input can buy under the route's pricing and fee rules. For Joe V1 and Liquidity Book trades, the pool charge leaves less input available for exchange. A quoted exchange rate therefore needs its token units and trade size. A fee percentage alone cannot describe the final exchange.

The expected output and minimum received amount have different meanings. Expected output describes the quote under the state used to calculate it. Minimum received sets the transaction's acceptance floor where the selected execution method enforces that limit. Neither amount establishes that tokens have arrived. Settlement requires successful execution and delivery to the intended recipient.

Liquidity Book fee calculations

Liquidity Book calculates swap fees within the price bins that serve a trade. A bin holds liquidity at a particular price. The Liquidity Book swap fee combines a base component and a variable component. These components determine the rate applied to each portion of input.

The base component

The base fee depends on the pool's base factor and bin step. The bin step describes spacing between adjacent bin prices in basis points. The implementation converts these configured inputs into its internal fee precision. The spacing value by itself is therefore insufficient to identify the fee rate. Pools with the same token pair can have different spacing and fee settings.

Open full-size image

The variable component

The variable fee uses a volatility accumulator, which tracks price-bin movement relative to a reference. Its calculation also uses the bin step and a configured variable-fee control. Trades that traverse further bins can change the applicable fee during the swap. Recent trading and the pool's timing parameters also affect the state used for calculation.

The accumulator has a configured cap, and reference updates use filter and decay periods. These settings belong to the selected pool. A quiet interval does not establish a universal waiting time for a lower fee, because another trade can change the pool state before execution.

Fees inside the input amount

For an input amount that already includes fees, the fee helper calculates the charge from that gross amount and the applicable rate. In decimal-rate notation, the relationship is fee = gross input × rate, with upward rounding in the token's smallest units. For a net input amount that excludes fees, the helper instead uses fee = net input × rate / (1 - rate), also rounded upward. These calculations use the relevant rate for the amount being processed, not one assumed rate for every bin.

Joe V1 and other pool fee rules

Joe V1 pools charge a 0.3% swap fee on the input amount exchanged through each V1 pool. That rate belongs to the V1 design; it does not describe every Liquidity Book pool or every route available through LFJ. The V1 pool also changes its exchange price as the trade alters its reserves. Fees and price impact both affect output, even though they arise from different mechanisms.

A route can include liquidity outside LFJ's own pools. The Meta-Aggregator draws routes from multiple aggregators, so the interface name does not establish every underlying pool's fee policy. A direct V1 rate, a Liquidity Book calculation and a routed external pool need their own applicable rules. The quote connects those rules to the selected trade size.

Swap page fees and Terminal deductions

The LFJ Swap page and trading Terminal apply different platform-fee policies. LFJ adds no platform fee to trades made through its Swap page. This policy leaves the routed pools' charges and network costs in place.

The premium trading policy charges a 1% platform fee on Terminal market orders, limit orders, dollar-cost averaging orders, stop-loss orders and buys through the Trenches page. LFJ applies that fee at execution and deducts it from the final output amount. Gas remains separate. A Terminal market order therefore needs a different cost comparison from a Swap page trade, even when both seek an immediate token exchange.

An output-denominated platform deduction and an input-denominated pool charge use different calculation bases. Keep their token units attached when reading the amounts. Subtracting an input-token fee directly from an output-token balance would mix unlike quantities.

Does a longer swap route always cost more?

A longer route does not always cost more overall, because additional pools can provide better exchange prices or more usable liquidity. A hop is an exchange through a pool along the token path. Each hop applies its own pricing and fee rules. The output of one hop supplies the input for the next, so nominal percentages alone do not establish the best final quote.

Crossing multiple bins inside one Liquidity Book pool is different from crossing multiple pools. Bin traversal changes the portions of liquidity and prices used within that pool. Pool traversal changes the markets and potentially the token units used along the path. Both affect the quotation, without necessarily requiring a separate wallet transaction for every internal step.

The LBQuoter can compare supported Joe pool versions for a supplied token path. Its result identifies the pairs, versions, intermediate amounts and fees used along that path. This quote calculation has a narrower scope than the Meta-Aggregator's search across aggregators.

Gas outside the pool fee

Network gas pays for transaction execution and remains separate from the pool's swap fee. On an Ethereum Virtual Machine, or EVM, network, execution gas depends on gas consumed and the effective gas price. Some networks also have additional fee components. An approval transaction can add another network charge when required. A smaller swap does not necessarily reduce execution work proportionally. When selling a network's native coin, the transaction still needs enough native balance to cover its network cost.

Token allowances and approval costs

An ERC-20 token allowance determines how much a particular spender may transfer from an account. ERC-20 is the token standard used by the relevant EVM contracts. This spending permission affects authorization and possible gas costs; it does not change the pool's pricing rule.

A sufficient existing allowance

An existing allowance can satisfy the transfer requirement when it covers the selected input for the correct spender. Permission for another contract does not automatically apply. Changing the route may change the spending contract, so allowance sufficiency belongs to the actual transaction path. Reading an allowance through a normal offchain call does not itself create an approval transaction.

A new spending authorization

An onchain approval changes the permitted amount and consumes network gas. The approval authorizes token spending without completing the exchange. A larger allowance permits more spending within its scope, even after the immediate trade. Native-coin inputs use a different transfer mechanism from ERC-20 inputs. The required authorization method depends on the selected token, contract and interface.

Is slippage tolerance an extra swap fee?

Slippage tolerance is an execution limit, not an additional percentage fee charged by the pool. It describes how much output deterioration the transaction permits relative to its quote. The pool's fee mechanism calculates charges independently. Increasing tolerance can allow a worse received amount without reducing those charges.

Price impact describes how the trade itself changes execution prices through available liquidity. Slippage also captures changes between quotation and execution. Liquidity Book holds a fixed exchange price within a bin, although swap fees still affect net amounts. A trade that needs further bins can encounter different prices. The within-bin property does not establish an unchanged price for the entire route.

Failed execution and token transfer charges

An included EVM transaction that reverts still pays for the gas it consumes. Reversion rolls back the transaction's exchange state changes. A separately completed approval remains a separate transaction.

An enforced minimum-output failure prevents settlement below that contract limit. A transaction deadline can also prevent execution after the permitted time. A failed receipt must be read differently from a pending transaction or a wallet prompt that never reached submission.

A fee-on-transfer token deducts an amount when tokens move. Such deductions arise from the token's rules and can affect what reaches a pool or recipient. They must remain distinct from the pool's trading fee. A displayed token symbol alone does not establish whether its contract applies transfer deductions.

LBRouter includes dedicated exact-input methods supporting fee-on-transfer tokens. The token-to-token supporting method checks the recipient's actual balance increase against the minimum output. This protocol capability does not establish that every aggregator route or interface supports the same token behavior. A fee estimate is useful only with an execution path that handles the affected transfers.

Like-for-like routes and the settled cost

A meaningful route comparison holds the chain, input token, input amount and output token constant. Compare quotes close together and use consistent slippage assumptions. Different trade sizes can traverse different liquidity and produce different effective fees. A smaller listed percentage may accompany less output when the route's exchange prices are worse.

Network costs need a common valuation unit before they can be compared with token proceeds. Include any required approval cost in that comparison without deducting pool fees twice from an already fee-adjusted quote. After execution, the receipt and actual token changes replace estimates for the completed trade. A settled transaction describes its own executed cost, while the next quotation uses the pool and network state available then.

What readers ask about Traderjoexyz swap fees