QUICK ANSWER
How do you swap a token on Cronos?
To swap tokens on Cronos, connect an EVM-compatible wallet to Cronos Mainnet, choose the token you will pay and the token you want to receive, request a live quote, review the route and minimum received, and confirm the transaction in your wallet. Cronos Mainnet uses chain ID 25 and native CRO for gas. A swap interface may send the trade directly to one decentralized exchange or route it through an aggregator. In either case, verify the token contract, provider, slippage, price impact, allowance and transaction target before signing. Keep enough CRO outside the trade to pay gas, and start with a small amount when using an unfamiliar token or route. On EmberSwap, the current production route uses an approved Obsidian provider through the EmberSwapRouter; additional providers will only be represented as live after separate review.
BEFORE YOU TRADE
Prepare your wallet for Cronos Mainnet
Cronos is an EVM-compatible network, so its addresses normally use the familiar 0x… format and its applications can work with EVM wallets. Cronos Mainnet is identified by chain ID 25. Do not confuse it with Cronos zkEVM, which is a separate network with a different chain ID, or with the Crypto.org/Cronos POS chain address format.
Your wallet needs native CRO on Cronos Mainnet to pay gas. A wallet can hold the token you want to sell and still be unable to trade if it has no native CRO for transaction fees. Avoid selecting the absolute maximum CRO balance: the quote may be valid while the wallet lacks enough remaining CRO to submit the transaction.
Wallet preparation checklist
- The selected network says Cronos Mainnet or chain ID 25.
- The receiving wallet address begins with
0x. - The wallet contains native CRO for gas, separate from the trade amount.
- The site origin and TLS connection are correct before you connect.
- You understand whether funds arrived through the intended network or bridge.
The official Cronos documentation is the authoritative source for current network details and wallet configuration. Treat copied RPC settings from social posts, advertisements or unsolicited messages as untrusted until checked against the official documentation.
THE TRANSACTION FLOW
Six steps for a Cronos token swap
- 01
Open the intended trading interface
Type or use a trusted bookmark for the domain. Phishing pages often imitate wallet buttons and token selectors. For EmberSwap, the production origin is
https://embercro.com. - 02
Connect without signing an unexplained message
A normal wallet connection exposes a public address and network. Read any later signature request separately. A token swap should ultimately require a transaction confirmation, not a request for a seed phrase or private key.
- 03
Select and verify both assets
Token symbols are not unique. Two contracts can use the same name or ticker. Compare the contract address with an official project source and inspect it on Cronos Explorer before trading.
- 04
Request a fresh executable quote
Quotes expire because reserves, routes and prices move. Confirm the amount, route, provider, fees, estimated output, price impact and minimum received. Refresh a stale quote instead of relying on an old screen value.
- 05
Approve the input token when necessary
ERC-20 tokens may require an allowance before the swap. Prefer a bounded allowance for the amount you intend to trade. Native CRO does not use an ERC-20 approval.
- 06
Verify the wallet transaction and submit
Check the network, destination contract, amount and gas estimate in the wallet. After submission, follow the transaction hash on Cronos Explorer. A pending or failed transaction is not a completed trade.
QUOTE LITERACY
Read the complete quote—not only the output
The largest estimated output is not automatically the safest or best executable result. A useful quote explains the full path between your gross input and the minimum amount the transaction is allowed to deliver. These fields matter:
Route and provider
The venue or routing service expected to execute the trade. An aggregator should disclose which production provider produced the quote.
Protocol and provider fees
Separate interface or router fees from fees charged by the underlying liquidity venue. If a provider fee is unavailable, it should not be guessed.
Price impact
The estimated effect of your trade on the execution price. Thin liquidity and large orders can increase impact sharply.
Slippage tolerance
The maximum adverse movement you accept between quote and execution. A wider tolerance increases execution flexibility and downside exposure.
Minimum received
The output floor encoded for the trade. If execution cannot meet it before the deadline, a correctly designed exact-input route should revert.
Estimated gas
The network cost estimate, paid in native CRO. Gas is separate from trading fees and may still be consumed by a transaction that reverts.
When comparing two routes, use the same input amount, token contracts, slippage setting and timestamp. A comparison is misleading when one quote omits fees, uses a different token representation or has already expired.
KNOW THE VENUE
DEX aggregator, direct DEX and centralized exchange
| Venue | What it does | Who submits the on-chain trade? | Primary checks |
|---|---|---|---|
| DEX aggregator | Requests or compares routes from enabled liquidity providers. | Your wallet, through an aggregator or routing contract. | Provider set, route, fees, router target and minimum received. |
| Direct DEX | Trades against pools or order systems operated by one protocol. | Your wallet, through that DEX’s contracts. | Pool depth, token pair, DEX contract and price impact. |
| Centralized exchange | Matches trades inside a custodial platform and handles withdrawals separately. | The exchange controls internal execution; the user requests withdrawals. | Custody, account access, withdrawal network, fees and jurisdiction. |
“Aggregator” describes routing capability, not guaranteed superiority. The result depends on which providers are enabled, whether their quotes are executable, and whether the same routes are available at confirmation time. A platform with one enabled provider should say so plainly.
RISK CONTROL
Verify the token, contracts and wallet prompt
Non-custodial does not mean risk-free. You control the wallet, but smart contracts, liquidity pools, provider APIs and tokens can fail or behave unexpectedly. A malicious token may block sells, take transfer taxes, change balances or imitate a known ticker. A verified contract proves the published source matches deployed bytecode; it does not guarantee economic safety.
Search results, social posts and wallet token lists can surface the wrong contract. Treat every copied address as untrusted until it matches an official project source and the expected Cronos Explorer record. If the issuer, contract controls, liquidity source or sell path cannot be understood, do not let interface availability substitute for due diligence.
Check the token address
Use official project sources and Cronos Explorer. Never rely on a symbol alone.
Check the transaction target
The wallet should show the Router or approved application contract you expected.
Limit allowances
Prefer exact or bounded approvals and review old allowances periodically.
Use a small first trade
A small transaction can expose network, token or route problems before more value is at risk.
Protect the seed phrase
No swap, support agent or administrator needs your seed phrase or private key.
Keep independent records
Save the transaction hash and use the explorer receipt as the execution record.
EMBER PRODUCT STATUS
How EmberSwap routes Cronos trades today
EmberSwap V1 is live as a non-custodial Cronos routing interface. Its production configuration uses the EmberSwapRouter at 0x095612aa8A0D54CA642b8e656A994AE17178Ffbc, a separate Fee Vault, and Obsidian as the first approved provider. The Router charges 20 basis points, equal to 0.20% of gross input, with an on-chain maximum of 25 basis points.
The browser validates provider responses and simulates the outer Router transaction before requesting wallet execution. For ERC-20 inputs, the interface requests an exact approval amount rather than unlimited approval. Production receipt indexing reconstructs confirmed swaps from Router events and on-chain evidence instead of trusting browser-submitted volume claims.
The routing engine can register multiple quote providers, but direct VVS routing and broader route comparison are not active production claims today. Native EmberSwap liquidity and DEX functionality are later product stages. Each additional route needs explicit implementation, contract review, operational monitoring and accurate public documentation before it is included in “best available” comparisons.
COMMON QUESTIONS
Cronos trading questions
Which token pays gas on Cronos?
Native CRO pays gas on Cronos Mainnet. Keep some CRO outside the trade amount so the wallet can submit approvals and swaps.
Is a DEX aggregator itself a DEX?
Not necessarily. An aggregator can route to external DEX liquidity without operating its own pools. EmberSwap starts as a routing layer; native DEX liquidity is a later, separately gated stage.
Why can the received amount differ from the quote?
Prices and pool reserves can change between quote and execution. Slippage tolerance defines the adverse movement accepted by the transaction, while minimum received is the output floor.
Can a verified token or contract still be risky?
Yes. Verification links source to bytecode but does not guarantee liquidity, fair token mechanics, secure administration or future value. Review the project and use amounts appropriate to your risk tolerance.