Skip to main content
KovaSwap prepares transactions; your wallet signs them. The interface never receives a seed phrase or private key. Use Kova markets for native Kova V2 and integrated liquidity on deployed networks. Use All EVM networks for LI.FI-powered same-chain aggregation on any currently supported EVM mainnet. Click the connected wallet balance above the input to fill the maximum available amount. When the input is Arc’s native USDC gas asset, KovaSwap leaves a small reserve so the wallet can still submit the transaction. Token artwork is resolved by contract address. KovaSwap uses reviewed local overrides first, then launchpad metadata discovered from the active chain’s configured integration, and finally falls back to token initials. A reused symbol never causes one token to inherit another token’s image.

​
Before signing

Review:
  • selected network and token contract addresses;
  • input amount and minimum output;
  • route and target contract;
  • pool fee and permitted slippage;
  • wallet approval amount;
  • gas estimate and price impact.
An ERC-20 approval is a separate transaction when the selected router lacks sufficient allowance. KovaSwap requests the trade amount rather than requiring an unlimited approval. Routed swaps include Kova’s disclosed interface service fee in the quote. See Routed EVM networks.

​
Transaction states

Submitted means the wallet broadcast a transaction. Confirmed means it was included successfully. A wallet popup alone is not proof of settlement; check the receipt on the network explorer.