Retik outlined pool pricing and exchange aggregation for token swaps
Last updated -
Retik described token trading through automated market maker pools and liquidity aggregation across decentralized exchanges. Pools supplied the assets and determined exchange prices through reserve-based rules. Aggregation sought favorable routes, including splitting a trade across exchanges. Limited liquidity could increase price impact or leave a requested swap without a usable route.
On this page
For a specified input amount, a swap quote estimates the output. Its meaning depends on the available liquidity, included fees, and execution conditions. The pricing model explains the mechanism; current availability of the full proposed service remains unconfirmed.
Bottom line: For a fixed input amount, a constant-product pool's exchange rate changes as the swap alters its token reserves.
Retik Swap pools and exchange routing
Retik Swap was described as the pool-based exchange component. The aggregation design had another job: comparing exchange liquidity and distributing a swap when several sources offered a better combined price.
Pool reserves and pricing
A liquidity pool holds tokens available for exchange. An automated market maker, or AMM, applies a pricing rule to those balances. Traders exchange tokens against the pool, and liquidity providers supply its reserves. Matching each trade with an individual seller is unnecessary under this model. The available balances remain essential because a pricing formula cannot supply missing assets.
Quotes and route selection
A decentralized exchange, or DEX, is a trading venue. An aggregator evaluates the exchanges that it can access, potentially dividing an input amount between sources. The Retik Wallet design placed exchange access within a wallet interface. Transaction signing, pool pricing, and route selection contribute different parts of the exchange process.
Combined output across exchanges
A split route combines the output from its component trades. Each part uses the pricing and available liquidity of its own source. The effective exchange rate comes from total final output divided by total starting input. It can differ from the rate displayed by any individual pool.
Dividing an order can reduce pressure on a shallow pool by using liquidity elsewhere. The benefit depends on the other sources, their fees, and the cost of executing the route. A direct pool trade can still offer the stronger quote. Aggregation searches existing liquidity; it adds no guarantee that every requested asset has an economical trading path.
Reserve balances and price impact
The constant-product model described for the swap uses the relationship x * y = k. Here, x and y represent the reserves of the two tokens. Their product is the invariant that the pricing rule constrains. In the simplified model without trading fees, adding input tokens requires reducing the output reserve to preserve that product.
Price impact is the change in the execution rate caused by the trade itself. A larger input relative to the reserves produces greater price impact in a constant-product pool. The opening reserve ratio describes the marginal rate for a very small trade. A larger trade changes that ratio during execution, so multiplying the entire input by the opening rate overstates output in the fee-free model.
A fixed input in a constant-product pool
A fixed input does not lock in the rate implied by the pool's starting balances. Consider a hypothetical calculation with 413 units of the input token, reserves of 8,260 input-token units, and 17,346 output-token units. The model excludes trading fees and network costs, and no other trades or liquidity changes occur during the calculation.
The starting reserve ratio is 17,346 / 8,260, or 2.1 output units per input unit. Multiplying 413 by that rate gives 867.3 output units. Constant-product pricing accounts for the change in reserves: output = 17,346 * 413 / (8,260 + 413) = 826 units.
The calculated output is 41.3 units below the opening-rate estimate, even before fees. The input remains fixed while the exchange rate changes along the pricing curve. Increasing the input relative to these reserves would further reduce the average output per input unit. Actual DEX quotes must also account for the applicable fee rules and current pool balances.
Which amounts matter when comparing DEX quotes?
DEX quotes are comparable when they describe the same assets, direction, input amount, and network. Expected output is the useful starting measure, followed by the costs that the quoted amount excludes.
Matching the trade
Token symbols alone do not identify a matching pair. The input and output contracts must refer to the same assets on the same network. Trade size also matters because a quote for a smaller input can face less price impact. Quotes taken at different moments can reflect changed reserves, even when their token selections match.
Fees and network costs
Pool trading fees can already be reflected in expected output. Network execution costs may appear separately, as can charges imposed by an interface or integration. Subtracting an embedded fee again would understate the quoted return. Comparing a network fee with output tokens also requires a consistent value basis. Keep estimated network spending distinct from the quoted output-token amount.
Expected output and the execution limit
Expected output is an estimate based on the quoted route and market state. A minimum-output condition sets the lowest amount acceptable during execution.
Slippage describes a change between the quote and the executed trade. Other transactions can alter reserves before a pending swap runs. Where the execution contract enforces a minimum output, a trade returning fewer tokens must revert. The displayed estimate and the enforced limit serve different purposes: one predicts output, while the other bounds acceptable execution.
Increasing slippage tolerance permits worse execution. It does not replenish a pool, remove the trade's price impact, or establish an available route.
A minimum-output check protects only the condition that it enforces. It does not insure the output token's future value or eliminate contract vulnerabilities. The protections available through a particular interface depend on its deployed contracts and transaction parameters.
Liquidity provision and pool-share tokens
The pool design assigned liquidity providers LP tokens and trading-fee rewards. An LP token represents a share of a liquidity pool, whereas swap output consists of the asset purchased. Providing liquidity leaves capital exposed to subsequent trades. Fee income depends on activity and the provider's share under the pool's rules; supplying assets alone does not establish a fixed return.
A constant-product liquidity position can lose value relative to holding the same deposited tokens when their relative prices change. This difference is commonly called impermanent loss. Fees may offset some or all of that difference, depending on trading activity. The pool's asset mix also changes as swaps add one token and remove another. A withdrawal reflects the updated asset mix and the pool's applicable redemption rules.
Pool trading, wallet balances, and service access
Pool trading, order-book matching, and wallet access describe different functions. A product combining them needs the liquidity and execution arrangements appropriate to each function.
AMM pricing and order-book orders
An AMM prices a trade through pool rules. An order book organizes bids and asks from market participants. Both can have insufficient depth for a requested amount. Aggregation can compare exchange opportunities without making every underlying venue use the same pricing mechanism.
Available tokens and allocated balances
A wallet balance supplies an input only when those tokens are transferable under the relevant contract rules. Vesting governs the release of allocated tokens, so an unreleased allocation is different from a spendable balance. Swapping, liquidity provision, and debit-card funding also have separate requirements.
Design scope and current access
Retik's roadmap placed desktop swap and staking services in the second quarter of 2025. The whitepaper set a planned milestone; Retik Finance also advertised access to Retik Swap in May 2024. These statements do not confirm current routes or delivery of the complete pool design. A usable quote needs available liquidity and an execution path for the requested assets. Compare quoted output and any enforced execution limit with total costs before choosing an available route.
Retik: questions and answers
Does a split DEX route require a separate signature for every pool?
A split route does not inherently require a separate wallet signature for every pool. A router can bundle multiple pool interactions into a single blockchain transaction. Token approvals may require additional prompts, depending on the token and interface. The number of liquidity sources alone does not determine the signing requirements.
Can exchange aggregation move tokens between blockchains?
Moving tokens between blockchains requires a cross-chain settlement mechanism. Comparing liquidity on several DEXs can take place entirely within one network. A cross-chain route needs compatible assets and settlement arrangements at both ends. A wallet's support for multiple networks does not establish that its swap routes connect those networks.
Why might a Retik token price be visible without an executable quote?
A displayed token price does not establish executable liquidity for a particular swap amount. A price feed can retain a historical observation or use a market outside the selected route. An executable quote requires supported assets and usable liquidity for the requested trade. Market state and routing restrictions can therefore prevent a quote even when a price appears.
Will a reverse swap restore the amount originally exchanged?
A reverse swap is a new trade at the pool's then-current pricing. It does not cancel the original exchange. Trading fees, changes in reserves, and additional network costs can prevent it from returning the original amount. Even an immediate reversal remains subject to the applicable fee and execution rules.
What happens to a token allowance if the swap fails?
A separately confirmed token approval is not reversed by a later failed swap. For a token that uses allowances, the earlier authorization can therefore remain in force after the swap reverts. An allowance applies to a particular spender and permitted amount. Its remaining scope depends on the token's rules, subsequent approval changes, and any spending.
Is the constant-product value a pool's dollar valuation?
The value k in x * y = k is the product of token reserves, not a dollar valuation. Valuing a pool in currency requires a price for each reserve asset and a consistent treatment of token units. The invariant describes the pricing relationship; it does not measure purchasing power or establish a token's market value.
Could a token's transfer rules change the amount received?
Transfer fees can reduce the amount that a pool or recipient receives, and transfer restrictions can prevent execution. A route needs compatible handling of those token rules. Any transfer charge follows the asset's contract and is distinct from the pool's trading fee. These conditions apply only to tokens that implement them.
Do I need LP tokens to use a liquidity pool for a swap?
An ordinary pool swap does not require ownership of the pool's LP tokens. Those tokens account for a liquidity provider's position. A trader supplies the swap input and uses liquidity already available in the pool. Any additional access or authorization requirements belong to the particular token, contract, or interface.