Swapping is where most people first hit the plumbing of crypto. You tap a button labelled "Swap," approve a transaction, and a different asset shows up in your wallet a few minutes later. Behind that button, though, two very different machines can be doing the work — with different costs, risks, and failure modes.
This guide walks through how swapping works inside Zelcore, when to use the built-in aggregator versus connecting to an on-chain exchange, and how to dodge the two most common ways beginners lose money on a swap: loose slippage and sandwich attacks.
Before you start
A few things are worth nailing down before you tap anything.
A "swap" just means trading asset A for asset B without an exchange account. But the swap button in Zelcore can route your trade through a cross-chain aggregator with a partner exchange, or you can connect Zelcore to an on-chain DEX and trade directly against a liquidity pool. Same word, different machines.
Zelcore is non-custodial. Whichever path you take, funds leave your address only when you sign a transaction. You never deposit to Zelcore itself — every swap is a signature from a key you control. If you haven't read them yet, what a wallet actually stores and seed phrases are the foundations that make this true.
Every swap costs you twice: the spread or provider fee baked into the quote, and the network fee on each chain involved. Cross-chain swaps — BTC to ETH, for example — pay two network fees because two different blockchains each settle their leg.
Three words to keep straight:
- Spread is the provider's profit, built into the quote before you see it.
- Slippage is the price moving between the moment you sign and the moment the trade executes.
- Price impact is how much your own trade moves the pool price.
Three distinct costs. Confusing them is how traders convince themselves a bad quote was actually fine.
Two ways to swap
Zelcore gives you two different paths to a swap, and choosing the right one matters more than any slippage setting.
In-wallet aggregator (QuickSwap)
QuickSwap is Zelcore's built-in aggregator. It queries multiple third-party non-custodial swap providers — Changelly is a publicly confirmed partner, with others like Kyber and CoinSwitch appearing over time — and shows you a quote without leaving the wallet UI. Under the hood, most of these providers run cross-chain non-custodial swaps: you send the source asset to a one-time deposit address, the provider sources liquidity (often on a centralised venue), and the destination asset lands at the address you control inside Zelcore.
Strengths: cross-chain in one step, no token approvals, simpler UX. Weaknesses: provider spread can run 0.5% to 3%+, quotes time out, and you are trusting the partner's internal routing.
WalletConnect to a DEX
The other path is connecting Zelcore to an on-chain DEX — Uniswap, PancakeSwap, Jupiter — through WalletConnect. Instead of a partner brokering the trade, you sign a transaction that trades directly against an automated market maker pool. The AMM is deterministic: you get the pool's algorithmic price minus slippage, no middleman spread. Part 6 covers WalletConnect mechanics in detail, but the tradeoff is worth stating up front: transparent on-chain pricing, but single-chain only and exposed to public-mempool MEV.
Rule of thumb: use QuickSwap for cross-chain trades or assets Zelcore natively holds. Use a DEX via WalletConnect for deep same-chain markets where you want the tightest price execution.
The in-wallet swap flow, step by step
- Open Zelcore and tap the Exchange button on the left toolbar, then choose QuickSwap.
- Pick the asset you are selling and the asset you are buying. Both must be enabled in your wallet — if you don't see the destination asset, enable it first in your asset list.
- Enter the amount to sell. Zelcore shows the estimated receive amount in real time as providers return quotes.
- Choose a rate type. Best Rate shows the most competitive rate available across providers. Fixed Rate locks the quoted rate for a short window at a slightly worse baseline, so you get exactly what you saw. By Provider lets you pick a specific partner.
- Check minimums and maximums. Each provider sets its own floor (usually a few dollars equivalent) and ceiling.
- Accept the third-party provider's terms when prompted. Most in-wallet partners are non-KYC under their limit thresholds.
- Tap Swap, then sign the outbound transaction from your source wallet. Your destination asset lands in your Zelcore address when the provider completes the swap.
Cross-chain swaps don't settle instantly. A BTC-to-ETH trade waits for Bitcoin confirmations before the ETH leg releases. Plan for a few minutes on fast pairs and up to an hour on slow ones.
Fixed vs floating, practically: fixed is insurance. You pay a slightly worse baseline, and market moves between signing and execution become the provider's problem. Floating is better on average and worse in volatile moments. On a quiet day with a major pair, floating wins. During a news spike, use fixed.
Slippage and price impact, in plain English
Slippage tolerance is the worst price you will accept. If execution moves past that bound on a DEX, the transaction reverts and you pay gas but get nothing traded. On an in-wallet swap, the provider just re-quotes you.
Uniswap's web app now uses dynamic auto-slippage — typically in the 0.1% to 5% range, calculated per swap based on live gas fees and trade size. They moved away from a single static default in favour of this per-transaction value specifically to make sandwich attacks harder, which tells you how important tight slippage really is. For deep stablecoin pairs like USDC to USDT, Uniswap's own example guidance is much tighter — around 0.05% on a $10M+ pool.
Why are stablecoin pairs so tight? Both sides track the same dollar peg, pools are deep, and arbitrage keeps them pinned. A $10,000 USDC-to-USDT swap typically shows price impact of a fraction of a basis point.
Exotic pairs are another world. A small-cap token paired only with ETH might have $50k of liquidity. A $5k trade is 10% of the pool and suffers huge price impact under the x·y=k curve — and no slippage tolerance saves you from price impact, because price impact is baked into the trade's math. On QuickSwap, slippage is abstracted behind a single quote, but the same physics applies: exotic-pair quotes come back noticeably worse than stable-pair quotes from the same provider.
Two habits that save money:
- Split large trades into smaller ones on thin pools. Each slice pays less price impact.
- Never accept auto-slippage above ~2% on a major pair. More slack is an invitation, not a safety margin.
Setting slippage to 50% to "just force it through" is the single most common way people get sandwiched for double-digit percentages.
MEV and sandwich attacks
MEV (Maximal Extractable Value) is the profit a block builder or bot can extract by reordering, inserting, or censoring transactions in a block. Sandwiches are the most common retail-facing form.
A sandwich has three steps. A bot spots your pending DEX swap in the public mempool. It front-runs you with a buy of the same token, pushing the price up. Your swap executes at the worse price. The bot immediately sells. Your loss is their profit.
Three conditions must hold for a sandwich to work: your trade must be visible before it lands (public mempool), your slippage tolerance must absorb the attack, and the pool must be liquid enough that reordering is profitable. Break any one and the attack fails.
This is a DEX-on-Ethereum/BSC/Polygon problem, not a QuickSwap problem. Aggregator swaps settle off-chain with a partner — there is no public mempool race to exploit.
If you are using WalletConnect to hit a DEX, you have mitigations. Private RPCs route your transaction directly to block builders instead of the public mempool. Flashbots Protect (rpc.flashbots.net/fast) is the most widely used — transactions are hidden from the public mempool and multiplexed to registered block builders, and the service refunds a share of captured MEV (and surplus priority fees) back to users when your transaction creates backrun opportunities. Alternatives include MEV Blocker and Blink, plus wallet-level "MEV Protect" toggles.
For the underlying primitives — wallets, gas, and token approvals — read the DeFi fundamentals guide before your first serious DEX trade.
Verification
After an in-wallet swap, check the incoming transaction in Zelcore's history and on the destination chain's block explorer. Confirm the amount, the address, and that it arrived from the provider's published hot wallet. Zelcore surfaces an order ID after you sign — save it. Every QuickSwap partner has a status page you can query by order ID.
Before a large swap, do a small test trade. Five dollars proves the flow, the address, and the provider. It is cheap insurance.
When a quote feels wrong, sanity-check it against a DEX aggregator in your browser. A quote that comes back 3% worse than everywhere else is a bad quote, not a lucky one.
Troubleshooting
Swap is stuck past the expected window. Look up the order ID on the provider's status page. Cross-chain swaps wait on source-chain confirmations — a BTC-leg trade can take 30+ minutes during fee spikes.
Received less than quoted on an in-wallet swap. Almost always a floating-rate quote that moved against you. Use Fixed Rate next time for certainty.
On-chain DEX swap failed. Usual suspects: slippage too tight (reverted), insufficient native gas token for the fee, a missing or expired token approval, or the router contract paused. Block-explorer error messages tell you which.
Balance didn't update after a cross-chain swap. The destination asset might be a token that isn't enabled in your wallet yet. Enable it in the asset list and the balance appears.
Quote looks far worse on one provider. Either the pair has poor liquidity with that provider, or the market is moving and quotes have gone stale. Refresh, or switch providers.
Next up
That covers the in-wallet swap path end to end. The other half of the swapping story is connecting Zelcore to DEXs and dApps directly, through WalletConnect. That is Part 6 — how the handshake works, what you are actually signing, and how to stay safe once your wallet is speaking to a website.
