Networks & swap limits

Start with what you see in the wallet

Choose the closest symptom to find the relevant checks. These steps help you interpret the interface; they do not require sending funds, approving tokens or signing a transaction.

• Unsure whether the wallet was saved: read the local storage and recovery limits. A visible balance or receive address does not verify a saved copy or recovery backup.
• Checking a receive address or QR code: use the address, network and asset checklist. A scanned address does not select the sending network.
• Missing or unavailable balance: compare the public account, selected network and asset. An error loading data does not establish a zero balance.
• Unfamiliar token or a claim link: read the unexpected-token checks before interacting with it.
• USDC balance differs from what you expected: check native USDC versus bridged USDbC before comparing token quantities.
• Funds are on Ethereum but you want to use Base: read swapping versus bridging. This quote form does not move assets between networks.
• ETH is visible but the form asks for WETH: read why native ETH and WETH have separate balances and check the Base token contract references.
• No quote or an error message: use the message-by-message quote checklist. For a first estimate, follow the Base WETH-to-USDC quote walkthrough.
• A wallet asks for a gasless signature: read the message-signing and Permit2 checks. Signing without a gas charge can still authorize token spending; viewing a RunixCoin quote does not require that permission.
• Disconnected a site but still see an allowance: read connections versus token approvals; disconnecting does not revoke spending permission.
• Output or fees look different than expected: read net output, interface fees and network gas, then minimum output and slippage. Estimates are not settlement guarantees.
• Failed transaction but less ETH: check included failures and actual gas charges; a quote error alone does not establish an on-chain fee.
• Empty history or a pending transaction: follow the transaction-hash and network checks. RunixCoin does not load blockchain history; use the actual network's explorer for a transaction submitted elsewhere.
• Looking for a swap button that executes: review current execution limits. RunixCoin provides quotes; swap execution is unavailable, and sending funds does not enable it.

Use only public account information for these checks. Read the wallet-security and privacy guidance before sharing troubleshooting details. Return to the RunixCoin wallet interface to review its current status.

Back to guide contents

Networks listed in the wallet

RunixCoin lists the following networks for its mainnet and testnet views. Listing a network does not mean every token, transfer or swap is available on it.

Choose an explorer for the network you are checking

Use the matching network below to search a full public account address or transaction hash. Each link opens an external explorer; you do not need to connect a wallet or sign a request to look up public activity. A result on one network does not establish a balance or transaction on another.

• Ethereum: Etherscan for Ethereum mainnet (1) or Etherscan for Ethereum Sepolia testnet (11155111).
• Base: BaseScan for Base mainnet (8453) or BaseScan for Base Sepolia testnet (84532).
• Polygon: PolygonScan for Polygon mainnet (137) or PolygonScan for Polygon Amoy testnet (80002).

Compare the network name, full address and asset contract before interpreting a result. An explorer lists public-chain activity; it does not show changes made only on a local fork. If a hash is missing, follow the transaction-status checks before retrying. Never enter recovery material into an explorer.

Explorer references: Ethereum explorer overview, Ethereum Sepolia resources, Base network details and Polygon network details.

The homepage network reminder is not a live indicator of the selected chain. Check the mode and network inside the wallet view you are using. The public Base quote form has a separate, fixed route; selecting test mode does not make its estimates Base Sepolia quotes. See the quote walkthrough for that distinction.

Choose the network mode before checking balances or a receive address. An address can look identical on several networks while holding different balances. Changing the selected network does not move or bridge assets.

Testnet tokens are for testing; a testnet balance is separate from your mainnet balance. A local fork is also a separate development environment: even if it uses Base's chain ID, activity there does not prove that a transaction works on Base mainnet.

Network references: Base network details, Polygon network details and Ethereum Sepolia configuration.

Back to guide contents

Base quotes and swap limits

The current quote flow requests WETH to USDC on Base mainnet (chain ID 8453). The asset browser is an illustrative catalog, not a list of supported swap pairs. Each View Base Quote Form button opens the same WETH-to-USDC form; it does not select the asset in that catalog row. For example, a Bitcoin row does not provide a BTC-to-USDC route. Compare the listed wallet networks separately from quote availability. Quote availability depends on the provider response and does not establish execution support.

ETH and WETH are different inputs

Native ETH pays Base network gas. WETH is a token representation of ETH and has its own token balance. An ETH balance alone does not supply the WETH amount requested by this quote form. Native ETH swaps are currently marked as unavailable in RunixCoin.

Before comparing token balances, check the Base WETH and USDC contract references; a matching symbol alone is insufficient.

Swapping versus bridging: Ethereum and Base balances

RunixCoin's WETH-to-USDC quote describes an exchange between two assets on Base. Bridging transfers assets between networks; it involves a different route and its own risks. Some services combine bridging and swapping, but RunixCoin does not provide a bridge or cross-chain swap flow. See ethereum.org's bridge explanation and risks.

For example, WETH held on Ethereum (chain ID 1) is not a Base WETH balance (chain ID 8453), even when both accounts have the same address. Selecting Base or requesting a quote does not move that WETH. Wrapping ETH also does not change its network.

Before interpreting an estimate, compare the source network and token with the intended destination network and token contract. Use the wrong-network checklist and Base token references. An ordinary transfer to your own address does not bridge funds. This guide explains the distinction; it does not verify or recommend a bridge route.

What a quote tells you

A quote estimates output for a particular amount and route. Output, gas estimates and minimum received can change. Review the selected network, input token, amount and displayed fees whenever requesting a fresh quote. A quote response does not grant token permission, sign a transaction or confirm settlement.

Do not treat an approval or signature as proof of a successful swap. A submitted transaction needs a transaction hash and a successful receipt on the intended network. RunixCoin's current quote and review screens should not be treated as confirmation that funds moved.

Back to guide contents

How to read a Base WETH-to-USDC quote in RunixCoin

This walkthrough covers the public Base Swap Quotes form, not a completed swap. It does not wrap ETH, bridge assets, approve tokens or submit a transaction. Provider availability is required to display a quote.

1. Open the public quote form. From the RunixCoin homepage, choose Explore Quotes on the Base Swap Quotes card. The form requests Base mainnet quotes (chain ID 8453); choosing another wallet network does not turn it into a quote for that network. Base Sepolia uses 84532, as listed in Base's official network details.
2. Check the pair before entering an amount. You Pay is WETH (Base) and Estimated Output is USDC (Base), after the interface fee. Native ETH and route reversal are unavailable. Enter a positive WETH amount in decimal notation with up to 18 decimal places (for example, 0.001). Exponent notation such as 1e-3 is not accepted. The form requests a quote automatically after valid input. If it asks you to unlock your wallet, no usable public wallet address was found. Never paste recovery material into an amount field.
3. Read the output and status. A successful response fills the Estimated Output amount and updates the exchange rate and fee rows. The status message above the amount fields shows quote progress, completion or an error, and is available to assistive technology. An error can also appear in the output field instead. An empty output or provider error is not a zero balance or a completed trade. Use the message-by-message quote checklist if the result is unavailable, or the network and balance checks for missing assets.
4. Review estimates as estimates. Compare the input, output, interface-fee disclosure and network-fee estimate, and minimum received. Minimum received shows Unavailable if the response omits a positive whole-number minimum in token base units, or gives a minimum greater than the quoted output. Missing values are not verified zero fees or guaranteed protection. Changing the amount clears the previous output and estimates. Wait for a fresh result; responses to earlier amounts cannot replace the latest request. See gas and ETH/WETH balances and allowances and slippage.
5. Stop at the quote. Check swap availability reports that execution is unavailable; it does not request an approval, signature or transaction. RunixCoin transaction execution remains unavailable, and a quote gives no transaction hash or settlement receipt. Do not approve a spender, sign a transaction or send funds to try to enable it. For a transaction submitted separately by another wallet, use the transaction-status guide.

The embedded wallet also has a separate Get Live Quote view. Its network-dependent messages do not change the public form's fixed Base route or establish mainnet execution support. This walkthrough reflects inspected interface behavior; it is not evidence of a successful live provider request or a real-money swap.

Back to guide contents

Base quote unavailable? Read the message before retrying

This checklist applies to the public Base Swap Quotes form. Read the status above its amount fields. An unavailable quote does not establish a zero balance, a failed blockchain transaction or a need to send funds.

Enter WETH amount / Use a decimal WETH amount

Enter a positive decimal amount such as 0.001, with up to 18 decimal places. Remove commas, spaces and exponent notation. The field represents WETH on Base, not a dollar amount or native ETH. This input check does not verify your balance.

Unlock your RunixCoin wallet first.

The public form could not find a usable public wallet address. Return to the wallet view and check the account you intended to use. This message does not mean the wallet is empty. Never paste a password, recovery phrase or private key into the quote form.

Wallet address is invalid. Reopen your intended wallet.

The public form found an address value but rejected its format or the all-zero address before requesting a quote. Reopen the intended wallet and compare its full public address with the account you meant to use. Never enter recovery material into the quote form. This format check does not verify account ownership, the selected network or a token balance.

Quote response is incomplete or invalid / invalid output or fee amount

The form rejected response data instead of displaying an estimate. Do not reuse an earlier output as a current quote. If the problem persists, stop and retry later; the message alone does not establish whether the problem is the provider or the integration.

Commission verification failed

The response did not pass the form's existing interface-fee check. Do not interpret this as a zero fee or approve anything to clear it. Read the current fee disclosure; execution remains unavailable.

Quote request timed out

The public form stops waiting after 20 seconds for the request and response body. Check your connection, then re-enter the intended WETH amount to request a fresh estimate. A timeout does not prove that the provider is offline or that a blockchain transaction failed. No approval or transaction is submitted by this quote request.

Quote unavailable or another provider/network error

No usable estimate is displayed. Check your connection and retry later. Switching the wallet network does not change this form's fixed Base WETH-to-USDC route. Use the network checklist if balances also look wrong.

Requesting a fresh estimate

After correcting the issue, re-enter the intended WETH amount. Valid input automatically starts a new quote request after a short pause; wait for the status to finish. Changing the input clears earlier output and estimate rows. Repeated retries do not enable swap execution.

If a quote arrives but Network Fee or Minimum Received says Unavailable, that individual estimate was missing or invalid. It is not a verified zero cost or guaranteed output. Follow the quote walkthrough and fee and minimum-output explanations. Do not send funds, grant an allowance or sign a transaction to troubleshoot a quote.

Back to guide contents

RunixCoin interface fee versus Base network gas

The current public WETH-to-USDC quote form discloses a 2% RunixCoin software interface fee included in the quoted output. Its display checks for a provider integrator-fee entry of 200 basis points (2%). This describes the existing quote interface; swap execution remains unavailable and no completed fee payment is established by a quote.

For a transaction submitted elsewhere that failed, see why an included failure can still cost gas and compare the actual receipt instead of relying on this quote estimate.

For a separately supported Base transaction, network gas covers execution and publishing data to Ethereum; an operator fee can also apply when configured. These costs vary independently of the RunixCoin interface-fee disclosure. See Base's official network-fee documentation and the ETH/WETH gas and balance guide.

Compare a fresh quote's input, net output, fee amount and minimum received together. The public form preserves all six USDC decimal places in output and fee quantities and rounds the net exchange-rate estimate to two decimal places. Incomplete or malformed quote responses and ambiguous customer or interface-fee outputs reject the estimate. Missing, malformed or out-of-range output and fee quantities reject the quote; an explicit zero fee quantity can be displayed but is not a promise of a free transaction. If the quote is unavailable or its fee check fails, do not infer a zero fee or a usable trade. Read the quote walkthrough and current execution limits before returning to the wallet interface.

Back to guide contents

Base gas fees and separate ETH / WETH balances

This is educational guidance, not an enabled swap tutorial. RunixCoin currently requests Base WETH-to-USDC quotes; native ETH swaps and transaction execution remain unavailable.

Why an ETH balance is not a WETH balance

WETH represents ETH as an ERC-20 token, with a balance recorded by a token contract. Native ETH and WETH are separate assets. For example, seeing 0.01 ETH does not mean you have 0.01 WETH to enter in this quote form. Check the input token's balance on Base before requesting a quote. A balance on Ethereum mainnet or Base Sepolia is separate from a Base mainnet balance.

Wrapping and unwrapping are blockchain transactions that cost gas. Selecting WETH in a form does not wrap ETH or bridge it between networks. Token symbols can be reused, so check the network and token contract rather than relying on a name. See ethereum.org's explanation of wrapped ETH.

What a Base network fee covers

Base fees include execution on Base and publishing transaction data to Ethereum. The total estimate can also include an operator fee when configured. Fees vary with the transaction and network conditions; a fixed dollar estimate is not a guarantee. Base's official network-fee documentation explains these components.

For ordinary wallet transactions on Base, native ETH pays gas; a WETH or USDC balance alone does not cover it. Check the full network-fee estimate before any transaction in a wallet that supports it. Network gas is separate from an application's interface fee and the swap amount. RunixCoin's displayed quote does not prove that gas, approvals or execution have been validated.

If the form reports insufficient WETH, compare the requested amount with WETH on the intended network. If data cannot load, follow the balance and quote checks below. Return to the RunixCoin wallet to review the network and current availability messages; sending funds will not enable an unavailable feature.

Back to guide contents

Identify WETH and USDC on Base before comparing balances

A token is identified by its network and full contract address, not just its name, ticker or logo. Use these official Base mainnet references for read-only comparison. This reference does not validate a provider response or enable a RunixCoin swap.

WETH on Base mainnet (chain ID 8453)

0x4200000000000000000000000000000000000006 — listed as WETH9 in Base's official contract reference. View the WETH token on BaseScan.

USDC on Base mainnet (chain ID 8453)

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 — listed in Circle's official USDC contract directory. View the USDC token on BaseScan.

Unexpected tokens and misleading error links

An unfamiliar token may appear when you inspect your public account on an explorer. Its presence, displayed price or familiar symbol does not establish that it is safe or supported by RunixCoin. Compare the network and full contract with the official references above.

Do not try to swap or transfer an unsolicited token to diagnose it. Scam tokens can deliberately fail and put a link in the error message, directing you to a site that requests a recovery phrase or token approval. Do not follow claim, unlock or cash-out links in token details or failure messages. MetaMask documents this pattern in its failed-transaction scam guidance.

Keep checks read-only. Review what approvals permit and the wallet-security guidance. An explorer listing does not add a RunixCoin route; the public form remains limited to Base WETH-to-USDC quotes with execution unavailable.

Native USDC versus bridged USDbC on Base

Base has both Circle-issued native USDC and a separate bridged token called USDbC, representing USDC bridged from Ethereum. They have different contracts. Circle explains this distinction in its native USDC on Base reference; Coinbase also describes USDbC as a bridged asset.

If an explorer shows USDbC while you expected USDC, inspect each token's full contract on Base and compare native USDC with Circle's directory linked above. Do not combine the two token quantities when checking a native USDC balance. A shared network or similar name does not make the contracts identical. Selecting a network does not convert USDbC into USDC. RunixCoin does not provide a USDbC conversion route; its public form requests WETH-to-USDC quotes and execution remains unavailable. See the current quote limits.

These are token contracts, not your wallet's receive address. Do not use this list as a payment destination. To inspect your holdings, open your own public account on the intended network's explorer and compare each token's full contract address. An unrelated token can reuse a familiar symbol; a matching name alone does not identify the asset.

Check the chain as well as the address: Base lists the same WETH9 address on mainnet and Base Sepolia, but balances belong to separate networks. Circle lists USDC mainnet and testnet contracts separately. Do not apply this mainnet reference to testnet balances or assume that a token on another chain is interchangeable.

Native ETH is separate from these ERC-20 token balances and pays ordinary Base transaction gas. See ETH versus WETH and gas, the wrong-network checklist and the quote-only walkthrough. Checking a contract on an explorer requires no approval or transaction signature. Return to the RunixCoin wallet interface to review current availability.

Back to guide contents

Token approvals and slippage: reading a swap review

This section explains general swap concepts. RunixCoin transaction execution remains unavailable; these checks do not enable an approval or swap.

What a token approval permits

An ERC-20 allowance records how many tokens a spender may transfer on your behalf. An approval sets that permission; it does not itself exchange WETH for USDC. The ERC-20 standard overview describes approval, allowance and delegated token transfers.

Before authorizing a request in a wallet, check the chain, token contract, spender address and spending amount against the intended transaction. An unlimited allowance permits more than a single swap amount. Prefer a permission limited to the amount you intend to spend, and reject a request you cannot explain. A familiar token symbol or an approval confirmation is not proof that the spender is correct or that a swap completed.

Disconnecting a site does not revoke token approvals

A wallet connection and an ERC-20 allowance are separate permissions. Disconnecting a site does not remove a token allowance already recorded on-chain. MetaMask explains this distinction and the gas needed for an on-chain revocation in its token-approval guidance.

Start with a read-only review: compare the account, actual network, full token contract, spender and current allowance. A permission on another network is a separate check. Do not infer revocation from a disconnected indicator or an empty activity panel.

RunixCoin does not provide an approval-revocation control. If you decide to change an existing allowance using another supported wallet or tool, verify its official address independently and review the request in your own wallet. Revocation requires an on-chain transaction and network gas; this guide does not submit it. No signature or recovery phrase is needed just to inspect a public allowance.

Gasless signatures and Permit2 permissions

A wallet message can be signed off-chain without paying gas at that moment. Some messages authorize token spending that can be submitted later. The absence of an immediate balance change or transaction hash does not establish safety. MetaMask explains this risk in its signature-phishing guidance.

Permit2 is one example, not a RunixCoin execution feature. It requires an existing ERC-20 approval to the Permit2 contract before it can move that token, then uses additional permissions that may be authorized by signatures. Its allowance and single-transfer modes have different scopes; a signature deadline and an allowance expiration are distinct limits. See Uniswap's Permit2 overview.

• Check the purpose and website. A spending permit is different from connecting a wallet or proving account ownership. Reject a request whose purpose you cannot explain.
• Read the permission. For a token-spending request, compare the account, chain, verifying contract, token, spender, amount and applicable deadlines with the intended action. A familiar contract name alone does not verify the full request.
• Keep quote checks read-only. RunixCoin's public quote form does not need a spending permit. Do not sign to clear a quote error or unlock unavailable execution. Disconnecting a site does not establish that a previously signed permission is invalid.

Slippage tolerance and minimum output

Slippage describes a change between the quoted and executed price. For an exact-input swap, minimum output is the least output the transaction accepts; execution below that limit reverts. A higher tolerance accepts a worse result. It is not an extra network fee and does not guarantee execution. Price impact is different: the trade itself changes the pool price depending on trade size and available liquidity. See Uniswap's swap concepts and execution protections.

Hypothetical exact-input example: if an estimate is 100 USDC and a 1% tolerance is applied to that output, the minimum is 99 USDC: 100 × (1 − 0.01) = 99. A transaction enforcing that minimum reverts if it would return 98 USDC. The tolerance does not deduct an extra 1 USDC as a fee. This is arithmetic for illustration, not a live quote, a recommended tolerance or RunixCoin's configured setting.

A minimum-output limit does not establish that the original quote is a good market price. The trade's own price impact can already affect that estimate; increasing tolerance does not remove it. See Uniswap's price-impact and slippage distinction. Compare interface fees and network gas separately; an included revert can still cost gas. RunixCoin has no public slippage-setting control, and its displayed minimum is an estimate, not a verified execution protection.

Review both estimated output and minimum received, token units, fees and any deadline before authorizing a supported transaction. If a quote expires or the amount changes, request a fresh review rather than relying on old figures. RunixCoin's displayed quote does not establish that these protections have been validated for execution. Check the current swap limits before returning to the wallet interface.

Back to guide contents

Checking a pending or failed transaction

This is general troubleshooting for transactions submitted from a wallet that supports them. RunixCoin swap execution remains unavailable. A quote or review message in this interface does not establish that a transaction was submitted.

RunixCoin activity panels do not load blockchain history. An empty panel is not evidence that an account has no sends, receives or swaps. Connecting a wallet does not enable history integration. For a transaction submitted elsewhere, use its transaction hash and actual network in the checks below.

1. Find the transaction hash in the submitting wallet. A quote reference is not a transaction hash. If you only requested a RunixCoin quote, there is no swap settlement to track. If another wallet reports submission without a hash, check that wallet's activity before trying again.
2. Use the explorer for the actual network. For Base mainnet (8453), check BaseScan; for Base Sepolia (84532), use Base Sepolia's explorer. Compare the sender, destination and transaction hash. These explorers are listed in Base's official network details. A local fork's activity is separate and will not establish a transaction on either public network.
3. Read the receipt status. A pending transaction has no receipt yet. A receipt status of 0x1 means success and 0x0 means failure. An approval's successful receipt confirms that approval, not a separate swap. Check the actual transaction and resulting token movements. See the Ethereum receipt reference.
4. If nothing is found, verify before retrying. Recheck the network and hash, then compare the wallet's activity with the explorer. A missing receipt alone does not identify the cause or prove success or failure. Avoid submitting a duplicate while the original status is uncertain.

Why a failed transaction can still cost gas

An included transaction that reverts rolls back its contract changes, but still charges for computation already performed. A failed swap therefore does not imply that no ETH was spent on network fees. See Alchemy's explanation of reverted transactions and MetaMask's failed-transaction gas guidance.

• Quote error or rejected wallet request: an interface message alone does not establish an on-chain fee. RunixCoin's public quote request does not submit a swap. Check the submitting wallet and a transaction hash before attributing a balance change to gas.
• Pending or missing receipt: the final outcome and actual fee are not established by an estimate. Follow the network and hash checks above; do not submit another transaction just to diagnose it.
• Included failed transaction: compare the receipt status, sender and network with the explorer's actual transaction fee. A reverted swap does not undo an earlier, separately confirmed token approval; check that approval's spender and allowance independently.

On Base, review the full network fee, including execution and Ethereum data costs, rather than treating the quote's gas estimate as the settled charge. Base's network-fee documentation explains these components. Gas and the RunixCoin interface-fee disclosure are separate; a failed-transaction message does not prove an interface fee was collected. These checks require public information, not a signature or recovery phrase.

Submission, inclusion in a block and finality are different stages; a hash alone does not prove success. The Ethereum transaction lifecycle explains the distinction. Return to network and balance checks if the account or asset looks wrong, and review RunixCoin's current limits before using the wallet interface.

Back to guide contents

Wallet security before checking balances or quotes

RunixCoin's current quote view does not enable swap execution. You do not need to send funds, approve a spender or sign a transaction to fix an unavailable quote. Start with the network, public-address and asset checks.

Use public information for troubleshooting

A public address lets an explorer show account activity; it cannot authorize spending. It can reveal balances and transaction history, so consider privacy before sharing it. A recovery phrase or private key controls funds. Never share either in messages, screenshots, reports or support requests, or enter them into a block explorer.

Receive address and QR code: check the network separately

The integrated wallet's Receive QR code contains the public address only. Its Copy Address control also copies only the address. Neither includes a chain ID, token contract or amount, so scanning or pasting it does not select or verify the sending network.

1. Compare the full address. Check the complete scanned or pasted destination against the account you intended to use, rather than relying on its shortened display. If copying fails, do not assume the clipboard contains the current address. A token contract from the token reference is not your personal receive address.
2. Check the network independently. Compare the receiving view with the sender's network selection. Base mainnet (8453) and Base Sepolia (84532) are separate networks even though both use the ETH label; see Base's official network details. Follow the wrong-network checklist if anything differs.
3. Check the asset and recovery status. Compare the intended asset's network and, for a token, its contract. A QR code does not verify a saved wallet or recovery backup; review the storage limits. These are read-only checks and do not require a transfer, approval or signature.

A public address identifies an account; it does not prove that you can recover or control it. See ethereum.org's account, key and address explanation. Sharing it can expose account activity. Receiving assets does not enable RunixCoin swap execution or convert ETH into the WETH used by the public quote form.

Local wallet storage and recovery limits

RunixCoin distinguishes a temporary wallet from one saved with Save Encrypted Wallet. Creating or importing a wallet is not, by itself, confirmation that encrypted storage has completed. The save step asks for a password and stores the encrypted wallet in the current browser; check its completion or error message before leaving the page. A static Settings notice is not a live storage-status check.

The interface does not establish that a copy exists in another browser or on another device. Keep your recovery backup independently of the browser copy. A quote, a balance or a public receive address does not verify that backup. Never share your password, recovery phrase or private key to check storage status.

Check the site and any wallet request

Check the full website address before opening a wallet. A connection request, token approval and transaction signature have different purposes. Read every request in your wallet and reject anything you do not understand. For token permissions, review the spender and allowance checks; a quote alone is not a reason to grant spending permission. Read the gasless-signature checks if a wallet requests a message signature. Review why disconnecting does not revoke an existing allowance.

Keep recovery material offline in a private place; avoid screenshots that may sync to cloud storage. A device password is not a substitute for a recovery backup. See ethereum.org's wallet security and scam-prevention guidance for recovery-phrase privacy, phishing and transaction review. These precautions do not establish that RunixCoin has been audited or that a transaction is safe.

Return to the RunixCoin wallet interface to read the current availability notices. Do not share secrets or send funds to someone promising to unlock an unavailable feature.

Back to guide contents

Checking missing balances or quote errors

Mainnet asset-list coverage: RunixCoin's mainnet list requests native ETH balances on Ethereum and Base and native POL balances on Polygon. This list does not fetch ERC-20 token balances, including WETH and USDC. A token missing from the list is not evidence of a zero balance, and a native-coin balance does not establish how many tokens you hold.

To check a token independently, choose the intended network in the mainnet and testnet explorer directory, compare your full public account address, then inspect the token holdings and full token contract. For Base WETH or USDC, compare the official contract references. Checking a quote does not check your token balance. These checks require no wallet connection, approval or signature.

1. Check the network mode and chain. Base and Base Sepolia are different networks. Compare the selected chain ID with the network you intended to view, using the wrong-network checklist.
2. Check the public address. Confirm the address shown belongs to the wallet you intended to open. Never enter a recovery phrase into a block explorer or share it to diagnose an error.
3. Check the asset. Native ETH and WETH have separate balances. A token name or symbol alone does not identify its contract or network. Compare the official Base WETH and USDC contract references.
4. Distinguish unavailable data from zero. An RPC or provider error does not prove your balance is zero. Check the same public address on the intended network's explorer and retry later if the provider is unavailable.
5. Read the status message. If the quote view asks you to unlock your wallet or says execution is unavailable, review the public quote error checklist and current limits. Do not send funds to try to clear an interface error.

If an explorer shows a token you did not expect, use the unexpected-token checks before following any links or trying to move it.

Back to guide contents

Wrong network selected? Check before sending anything

A missing balance can mean you are viewing a different network or account. Start with read-only checks; sending another transaction is not a diagnostic step. For Ethereum, Base or Polygon, choose the matching mainnet or testnet in the explorer directory.

1. Identify the intended network. Compare the wallet's network mode and chain with the record of the original transfer. Base mainnet uses chain ID 8453; Base Sepolia uses 84532. Both label their gas currency ETH, so that label alone does not distinguish them. See Base's official network details and the wallet network table.
2. Compare the same public address. Use BaseScan for Base mainnet or Base Sepolia's explorer for the testnet. Check the full address against the account shown in your wallet. An address on one explorer does not establish a balance on the other network. Never enter a recovery phrase or private key into an explorer.
3. Check which asset arrived. Native ETH and token balances are separate. If you expected WETH, inspect its token contract on the intended network rather than relying on the ticker. An ETH balance is not a WETH balance; review gas and separate ETH/WETH balances.
4. Recheck the view after selecting the intended network. Switching a network changes what you view; it does not bridge assets, convert test tokens into mainnet funds or move a past transfer. If an explorer shows the expected balance while the interface cannot load it, distinguish unavailable data from zero and retry later.

If a transfer was sent on a different network than intended, first establish its actual network, destination and transaction status. This checklist does not recover or reverse a transfer. Do not send a second payment or share recovery material with anyone promising to fix it.

RunixCoin quote limitation: The public quote form remains fixed to Base WETH-to-USDC even when another wallet network is selected. A correct network selection does not enable execution. Review the quote walkthrough and current limits before returning to the wallet interface.

Back to guide contents