Swap help.
Check the assets, review the quote, then confirm in your wallet.
This guide is for DogeOS Chikyū Testnet, chain ID 6281971. Use testnet assets. A quote needs no wallet; signing does.
- Choose what to pay and receive, then enter the amount.
- Check the full token address and network in token details. A familiar name, symbol or icon does not verify an ERC-20 issuer.
- Connect your wallet when you are ready to review and sign.
Swap or Trade?
Both are the same swap: the same routes, prices and contracts. Swap is just the ticket, for when you know what you want. Trade puts the market beside it: DOGE/USDC candles read from the chain, each pool’s price, and your own buys and sells on the chart. Your trades show on either page, because they’re read from your wallet’s history.
Which DOGE, and what does importing a token do?
DOGE is the native currency on this network and has no ERC-20 contract address. Fetch’s router routes it through DogeOS’s native DOGE token, so there is nothing to wrap.
A badge in Fetch’s list means the exact contract matches its source: DOGE is the native currency, and LBTC, WETH, USD1, USDC and USDT are the contracts the official DogeOS testnet faucet sends. Look-alike tokens with the same symbols exist on the network. A badge identifies an asset; it is not a safety rating. Import token reads an address’s metadata and asks you to review it and acknowledge the warning. It does not verify safety, approve spending or send a transaction. Removing an import removes the browser-list entry, not your wallet holdings.
Review your quote.
Estimated output can change. Under the estimate, Fetch shows the least you will receive and the signed price impact. Open the rate line for slippage, deadline, pool fees and the route. When you choose Review swap, a review sheet repeats the terms and an estimated network fee before your wallet opens.
- Minimum received
- The lower output limit used for the request, based on your selected slippage.
- Slippage
- Your allowed output movement. Raising it is not a guaranteed fix for a failed trade.
- Price impact
- How much this trade moves the price against you, shown as a loss (for example −2.4%). From 1% it is marked as a caution, from 3% with a banner, and from 15% as critical: the review sheet then leads with Go back, and swapping anyway needs your acknowledgment.
- Route
- The assets and pools used for this quote. Pool percentages are allocations within each hop, not partner fees.
- Network fee
- The review sheet estimates it from a read-only dry run of the exact transaction. If the network rejects the dry run, Fetch says the swap is expected to fail and offers a fresh quote instead of opening your wallet. Your wallet’s fee is the final one.
- Token warnings
- A number on a token means Fetch found specific problems with a token it hasn’t verified, such as unverified source code, a contract under a week old, most supply held by a few addresses, or a reused verified symbol. They are facts, not a safety rating.
The ring around the refresh button empties over 15 seconds and refills with each new quote. Previous quote updating or NOT EXECUTABLE means the displayed quote cannot be used to swap. Wait for a current quote or use the refresh control. If the quote gets worse while the review sheet is open, accept the new quote before continuing. A listed token can still have no route.
What about WDOGE?
Legacy WDOGE is no longer listed. When the best route uses a WDOGE pool, the route shows a 1:1 “Wrap to WDOGE” or “Unwrap WDOGE” step with no pool fee, inside the same swap. Keep enough native DOGE for the network fee; an estimated output is not a gas estimate.
Approve, then swap.
With an ERC-20 pay token, Fetch may first ask you to approve spending. An approval gives the router an allowance; it does not swap the token.
- Review the spender and allowance in your wallet. Unlimited approvals are off by default; enable them only if you intend that allowance.
- After approval confirms, return to Fetch and review the current quote.
- Start the swap separately and review that transaction in your wallet.
- Use the matching successful receipt to confirm the result. Open the explorer for final execution details.
Native DOGE input does not require an ERC-20 spending approval. Network fees may apply to each transaction, including a reverted transaction.
Check before trying again.
If the result is pending or unknown, check the original request. It may still be pending or already confirmed. Do not submit the same trade again from another tab or device.
Look for Unfinished requests under the swap. Match the displayed account and network to the wallet you used.
I have a transaction hash
- Choose View on explorer to inspect the transaction on the configured testnet.
- Choose Check status in Fetch. This reads the result; it does not sign or submit another transaction.
- If no receipt is available, wait and check again. Another request from this account stays blocked while the outcome is unresolved.
A successful matching receipt confirms the operation. Approval confirmation still requires a separate swap request.
I have no hash, or reloaded with the wallet prompt open
- Open activity in the originating wallet. Check whether it submitted the request.
- If it did, copy the full hash into Transaction hash from your wallet and choose Check transaction.
- Fetch checks that the transaction matches the original account and request before attaching it. An unrelated or older hash cannot resolve the request.
If your wallet sent nothing, open My wallet didn’t send anything on the saved request. After a one-minute wait, Fetch checks that this account has sent no transaction since the request, then releases it. If the account has sent something since, paste that transaction’s hash instead. A quote refresh or new wallet connection does not release a request, and clearing site data does not cancel one.
The wallet rejected it, or the transaction reverted
A wallet rejection before returning a hash is shown as cancelled. If you already have a hash, check it first; a later error does not cancel a submitted transaction.
Reverted onchain means the receipt reports that the request did not complete. Network fees may still apply. Review the error and a fresh quote before another attempt; do not automatically increase slippage.
I sped it up, cancelled it or replaced it in my wallet
Fetch may detect a replacement when the RPC can still find the original transaction. A confirmed repricing can complete the same operation. A cancellation or different replacement does not confirm the original swap.
Use the explorer links to compare the original and replacement hashes. If Fetch cannot verify the outcome, the request remains unresolved. Fetch has no cancel or speed-up transaction control.
Other issues.
- No route
- Check the pair and amount. Listing or importing an asset does not create liquidity.
- Quote failed
- Retry the quote request. A previous quote cannot be used while the new request has failed.
- Network switch
- Check the wallet prompt, then use Retry network switch. Review the account and network again.
- Balance unavailable
- Use Retry balance check. A missing balance is not a zero balance.
- Allowance unavailable
- Use Retry allowance check. Do not assume that spending has already been approved.
- Expired or insufficient output
- Review a fresh quote and the error before retrying. If a hash exists, check its receipt first.
What this browser remembers.
Fetch saves each request in this browser, on this device and site address, until its outcome is checked, so a reload can’t lose it. Unfinished requests show under the swap and have no time limit. Finished ones aren’t listed there: your trades are on the chain, and both the wallet (Your trades) and Trade (choose Mine under the chart) list them on any device.
Clearing site data, using another browser or opening a different preview address removes or bypasses that local history. It does not cancel a transaction. Always check the originating wallet before starting over elsewhere.
If browser storage cannot be read or wallet requests cannot be coordinated across tabs, Fetch stops before signing. Use Check browser storage again after resolving the browser issue. If one saved record can’t be read, Fetch sets it aside and asks you to check your wallet before removing it; other records keep working. If saving fails during a request, keep the page open and copy any returned hash.
What is saved, and what has been verified?
The activity record saves the account, network, operation, timestamps and hash when available, plus data used to match the original request. It does not save swap amounts, token selections, credentials or private keys.
The frontend has unit and read-only preview checks. Signed wallet, reload and replacement cases still need testnet validation; this guide is not a contract security audit. Read the developer recovery reference for implementation limits.