SunSwap turns your token selection into a trade by quoting pool liquidity, then submitting a signed swap to smart contracts; the displayed output remains conditional until execution. On SunSwap, SunSwap liquidity pools supply the assets behind that quote, while trade size, routing, and on-chain changes can affect what reaches your wallet.
SunSwap Quotes Follow Liquidity, Not Orders
A quote reads available liquidity in smart contract pools, rather than matching your trade with another person’s order. Liquidity providers deposit assets that traders exchange through those pools. You select an input token, an output token, and an amount; the exchange calculates how much output the available pools can provide at that moment.
- Pool depth: More usable liquidity near the current price usually lets a trade move the price less.
- Trade size: A larger input consumes more of that liquidity, so its average execution price can be worse than the price shown for a small trade.
- Route: A direct pool may handle the swap, or the trade may pass through an intermediary token and a second pool. Each leg has its own liquidity and fee.
Pool design matters as well. In a V2-style pool, exchanging assets changes its reserves and therefore its price. SunSwap V3 concentrates liquidity within price ranges, so a pool’s total deposits do not tell you how much is usable for your trade. The route and expected output are better evidence than the mere existence of a trading pair.
What Does the Displayed Output Actually Promise?
The displayed output describes current execution; it does not promise that exact receipt. It accounts for the route’s pool prices, the effect of your trade on those prices, and pool fees. Price impact is the change your own trade causes as it draws from pool liquidity. It is already part of the quote.
Slippage tolerance addresses a different change: execution becoming worse between the quote and the on-chain swap. The transaction uses that tolerance to set a minimum acceptable output. Other trades can change pool balances before yours executes, and a route with several pools has several places where conditions can move. If the route cannot satisfy the transaction’s limits, the swap fails instead of delivering an output below the limit.
Read minimum received alongside expected output before signing. It is the useful decision point: if that minimum would be an unacceptable exchange, reduce the trade size or inspect another available route. Raising tolerance merely permits a worse result; it does not create liquidity or improve the quoted price. Tokens that deduct an amount on transfer or restrict transfers can also change the effective receipt or prevent execution.
The Wallet Signs Permissions and the Swap
Your compatible TRON wallet selects the account, supplies the input assets, and signs the required transactions. For a TRC-20 input token, the swap contract may first need an allowance to spend it. That approval grants permission and can require its own transaction; it does not exchange any tokens. The later swap signature authorizes the actual trade under its stated conditions.
Separate trading costs from network costs when reading the wallet prompt. Pool fees reduce the output available through each leg of the route. TRON contract execution also uses network resources, including Energy and Bandwidth; the amount depends on the contract work and resources available to your account. If resources are insufficient, TRX may be consumed. A separate approval adds its own network cost, even though it produces no swap output.
Settlement Requires Execution and Receipt
A swap settles when its transaction succeeds on TRON and the output tokens reach the recipient. After you sign, the wallet broadcasts the transaction. The contracts then take the permitted input, exchange it through the selected pool or pools, update pool balances or active liquidity, and deliver output only if the execution conditions hold. A signature shows intent; a broadcast shows submission. Neither alone proves delivery.
The transaction can fail if a pool changes enough to breach minimum received, a required transfer fails, or a token’s behavior conflicts with the route. A wallet notification may arrive before you have confirmed the result. Look for a successful on-chain transaction and the actual token receipt in the destination account; together they establish what settled and how much arrived.
Make minimum received your standard pre-signing check, then compare it with the receipt after execution. That small habit keeps the quoted estimate, the amount you authorized as acceptable, and the amount delivered from becoming one confusing number.
Top comments (0)