How to Know What SyncSwap Can and Cannot Undo

SyncSwap swaps are reversible only before they become confirmed on-chain state changes. A user can edit or reject a quote, cancel a still-pending transaction, and later revoke a token allowance. Once a swap or approval is confirmed, it cannot be rolled back; the practical remedy is a new transaction. The interface shows the quote, route, fees, and minimum received before signing.

1. Confirmation makes a SyncSwap swap final

A confirmed SyncSwap swap is final at the protocol level because it has already changed balances and pool reserves on the network. The exchange is non-custodial: the wallet signs an instruction, and a smart contract executes it. SyncSwap’s protocol documentation describes four pool models—Classic, Stable, Aqua, and Range—along with a router that selects routes across its liquidity system. See the SyncSwap DEX documentation for the current architecture.

After confirmation, the interface cannot take the received tokens back, restore the old price, or return the original assets automatically. A second swap can trade the output token back, but that is a new market transaction with another fee, another price, and possible price impact. It is not an undo button.

“Once a block is finalized it could only ever be changed by a network level attack that would cost many billions of dollars.” — Ethereum.org transaction documentation

The same principle applies to a confirmed liquidity action. Adding liquidity, withdrawing liquidity, minting LP tokens, or burning them creates new state changes. A user may later withdraw a position if the protocol and position rules allow it, but the withdrawal does not rewind the original deposit. The amounts can differ because fees, pool reserves, and token prices have changed.

Two controls keep a SyncSwap mistake from settling

Two controls can stop a SyncSwap mistake before it settles: refusing the wallet signature and replacing a pending transaction. The first is certain because nothing has been submitted. The second is only an attempt, because the original transaction may be included before the replacement reaches the network.

Before signing, the user can change the token pair, amount, route, slippage setting, or recipient. Closing the tab or rejecting the wallet prompt leaves no swap to reverse. Connecting a wallet is also not the same as approving a token or sending a transaction; the connection is an interface session, while approvals and swaps are on-chain actions.

For the live quote and the wallet action that follows it, https://syncswap.app/ is the interface that shows the selected pair, estimated output, route, and minimum received before the signature request. That review matters because a Smart Router may use several pools, hops, or split paths, so the final contract call may be more complex than a simple token-for-token exchange.

Once submitted, a transaction normally enters a pending pool. A wallet may let the user cancel it by sending a replacement transaction with the same nonce, or speed it up by resubmitting the same action with a higher fee. MetaMask’s pending-transaction guidance states that cancellation can only be attempted while the transaction is pending and that a confirmed transaction cannot be reversed.

The signed request has three different states

Every wallet request sits in one of three states: unsigned, pending, or confirmed. The action available to the user depends entirely on which state applies.

StateWhat can still changeWhat cannot be undoneUnsignedPair, amount, route, slippage, recipient, or the decision to rejectNothing on-chain has happenedPendingA cancellation or replacement may win the same nonceGas already spent on earlier actionsConfirmedA new swap, withdrawal, or approval can create a different resultThe recorded transaction and its state change“Pending” does not mean “reversible.” It means the network has not yet accepted the transaction into a block. A replacement must be accepted first. If the original swap confirms, the replacement is no longer an undo; it will usually fail, be dropped, or become a separate later action.

Nonce management also matters. A wallet account generally processes transactions in nonce order, so an older stuck transaction can block newer ones. Replacing the wrong nonce may not clear the queue. The safest approach is to identify the oldest pending transaction and use the wallet’s built-in replacement controls where available.

Approval is permission, not a transfer

An approval grants a spender permission to move tokens; it does not itself move those tokens. The ERC-20 standard defines approve as allowing a spender to withdraw up to a stated amount and defines allowance as the remaining amount that spender may withdraw. The ERC-20 standard documents both functions.

This creates an important distinction. A confirmed approval cannot be erased from the blockchain, but its permission can be changed with another transaction. Setting the allowance to zero, or reducing it to a smaller amount, prevents future transfers above the new limit. Wallets and allowance-management tools may describe this action as revoke.

Revoking does not recover tokens already spent. If a malicious or mistaken contract has already used the allowance, the later zero approval only stops additional transfers. It also costs gas because the revocation is a new on-chain state change. A user should therefore treat an approval prompt as seriously as a swap prompt and check the token, spender, and amount.

A failed transaction changes nothing, but still costs gas

A reverted transaction leaves the intended swap state unchanged, but it can still consume network resources and incur a gas charge. The token output is not delivered, and the pool should return to its prior state for that transaction, but the fee treatment depends on the network and wallet.

Slippage protection is designed for this boundary. SyncSwap’s trading guide defines minimum received as the least output accepted under the selected slippage setting. If the market moves beyond that limit, the transaction reverts instead of completing at a worse rate. The SyncSwap trading guide also explains that pool fees are deducted from the displayed output.

That protection prevents an unacceptable execution; it does not reverse a successful one. A high slippage setting may allow a trade to complete at a poor price, while a low setting may cause a legitimate trade to revert. Neither setting makes a confirmed swap reversible.

Six checks tell a SyncSwap user what can still change

Six checks are enough to separate a changeable decision from a final transaction.

1. Choose the network and token pair.
2. Enter the amount and inspect the quoted output.
3. Review the route, price impact, fees, slippage, and minimum received.
4. Approve only the required token allowance when the wallet requests it.
5. Sign the swap only after checking the recipient and contract action.
6. Check the transaction status and act before confirmation if cancellation is necessary.

When a wallet prompt is unclear, the boring way is better than the clever one: I reject it, reopen the route, and inspect the spender. The practical rule is simple: edit before signing, attempt replacement while pending, revoke permissions with a new approval transaction, and treat every confirmed swap as permanent.