Skip to main content

Swap

Flipit Swap is available after a token graduates and its canonical pool has been bootstrapped.

Supported routes​

  • zkLTC → Token
  • Token → zkLTC
  • Token A → Token B through wrapped zkLTC internally

The router handles wrapping and unwrapping. Users interact with zkLTC, not a separate wrapped asset.

Quotes and execution​

Swap quotes come from live contract state. The connected wallet signs the transaction directly. The router forwards output to the supplied recipient and is designed not to retain user assets after a completed swap except accidental transfers.

Approvals​

ERC-20 input routes require token allowance to the router. Native zkLTC input does not require an ERC-20 approval.

Slippage and deadline​

The UI computes a minimum acceptable output from the quote and selected slippage tolerance. Router methods also include a transaction deadline so a stale swap cannot execute indefinitely.