Remy Froissart, CNRS

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.



img  width: 750px;  iframe.movie  width: 750px; height: 450px; 
[[https://extension-wallet.io/coin98-web-guide.php|Coin98 Wallet seed phrase]] wallet extension setup troubleshooting guide



Coin98 Wallet Extension Setup Fixes for Common Installation and Connection Issues

If the add-on fails to appear in your browser's toolbar after installation, immediately check the extensions management page (chrome://extensions or about:addons). Ensure the toggle is activated and, for Chromium browsers, confirm the pin icon is clicked to make it visible. A required browser restart is often the simplest fix for this visibility issue.


Connection problems frequently stem from network-level interference. Configure your firewall or security software to allow traffic for the application, and consider disabling conflicting plugins like aggressive ad-blockers or other crypto asset tools temporarily. Using a clean browser profile isolates the problem from corrupted cache or conflicting data.


Persistent "initialization" errors may relate to stored local data. Navigate to the utility's settings, find the option to reset or clear its internal data, and re-import your credentials. Before this, verify you possess your complete 12 or 24-word secret recovery phrase, as this action will be necessary for restoration.


For transaction signing failures, always check the originating dApp's network setting against your active profile's network. A mismatch is the most common cause. Ensure your node RPC settings within the tool are configured correctly, or switch to a reliable public endpoint if custom nodes are unresponsive.

Browser Compatibility and Extension Installation Errors

Confirm your browser version is current; Chrome 90+, Firefox 88+, or Brave 1.32+ are required for full functionality.


A corrupted browser profile often causes the installer to fail silently. Create a fresh profile via `chrome://settings/manageProfile` or `about:profiles` in Firefox and attempt the installation again from the official store.


Security software or enterprise group policies can block CRX file installation. Temporarily disable antivirus real-time protection for the install, and check your OS administrative templates for any restrictions on software from unknown publishers.


If the add-on icon vanishes after installation, it's likely pinned to the browser's extensions menu. Access `chrome://extensions/` or `about:addons`, locate the utility, and click the pin icon to restore it to your toolbar.


Manifest version mismatches trigger specific errors. The software is built for Manifest V3; older browsers or forks still operating on V2 will reject it outright.


Hardware acceleration conflicts can freeze the interface during initialization. Disable this option in your browser's advanced system settings, restart, and test the plugin's performance.


Persistent "Corrupted" errors necessitate a clean download. Remove the add-on completely, clear your browser's cached files, and obtain a fresh copy directly from the Chrome Web Store or Firefox Add-ons portal.

DApp Connection Failures with the Extension

Force a network refresh within the DApp's interface; many decentralized applications cache your previously used chain, which can conflict with your current selection. Manually switch to a different network and then back to your intended one directly on the DApp's site. This action clears the stale RPC data and prompts the application to request fresh connection permissions from your crypto tool.


Check your active network against the DApp's supported chains. A mismatch is the most frequent culprit. Your portfolio manager might be set to BNB Smart Chain while the application only operates on Polygon. Verify the DApp's documentation and manually align your selected chain in the browser plugin's pop-up window before attempting to reconnect.


Adjust your privacy shield settings. Overly restrictive tracking protection or script blockers (like those in Brave or with extensions such as uBlock Origin) can prevent the necessary communication between the website and your financial plugin. For the specific DApp's domain, temporarily disable these shields and allow scripts to run. Also, ensure you are not using a VPN or proxy service that the DApp's geofencing might block.


If the problem persists, the issue may lie with the DApp's own RPC endpoint. Try these steps in order:Clear your browser's cache and hard reload the page (Ctrl+Shift+R).Check the DApp's official social channels for known RPC outages.Manually add a custom RPC for that network in your plugin's settings, using a reliable public node from sources like Chainlist.


Re-establish the connection link. Go to your browser's settings, find the site permissions for the DApp, and revoke its connection to your financial plugin. Then, initiate a fresh link by clicking the "Connect" button on the DApp and carefully authorizing the request. This resets the handshake protocol.

Seed Phrase Wallet Recovery Not Functioning

Immediately verify you are entering the 12 or 24-word mnemonic phrase in the exact, original order, with single spaces between each term.


Check for typos; common errors include confusing 'b' with 'd', 'l' with 'I', or 'seed' with 'said'. The system is case-insensitive, but spelling must be perfect. Manually type each word–avoid pasting from a text file, as hidden formatting characters can corrupt the input.


Confirm the derivation path. Different software uses distinct paths like m/44'/60'/0'/0 for Ethereum or m/44'/501' for Solana. If your mnemonic was created elsewhere, the default path in this interface might be incorrect. Access the advanced recovery settings to manually specify the correct path used by the original application.


Were multiple accounts generated from this mnemonic? If the first derived address appears empty, try incrementing the account index (e.g., Account #1, #2) during the process. Your assets might be linked to a subsequent account, not the initial one.


Attempt the procedure in a private/incognito browser window. This eliminates potential conflicts from other browser add-ons or cached site data that could interfere with the restoration logic.


If all steps fail, the mnemonic may be incomplete or from a different standard (e.g., a 13th or 25th passphrase was used). Re-examine your backup source; a single missing word renders the sequence invalid.

Transactions Stuck or Missing from the Extension

First, verify the transaction status directly on the blockchain explorer for your active network.


Pending transactions often result from insufficient gas. Manually increase the gas price (Gwei) for a higher chance of confirmation; a 20-30% bump is typically effective. Abandoned pending actions can be overridden by sending a new transaction with the same nonce and a significantly higher gas fee.


If balances appear incorrect, the issue is likely a synchronization delay. Force a refresh of your asset list. Manually add the custom token contract address if a new asset remains invisible.


SymptomPrimary ActionParameter to Adjust
Transaction pending for hoursSpeed up transactionGas Price (Gwei)
Token transfer not showingImport token manuallyContract Address
Incorrect native balanceSwitch network &amp; backRPC Endpoint


Network congestion causes delays. Check current average confirmation times for that specific chain before taking further action.


A corrupted local cache stores outdated data. Clearing this stored information forces a fresh sync with the network, resolving most display glitches.


Persistent problems may stem from an incompatible RPC node. Switch to a custom, reliable endpoint for better connection stability and data accuracy.

Network and RPC Configuration Problem Resolution

Verify the exact RPC endpoint URL and chain ID on the network's official documentation or a trusted community resource; a single incorrect character will prevent connection.


Manually add the network using the correct parameters if it doesn't appear in the default list. This requires entering all data precisely:


Network Name (e.g., Arbitrum One)
New RPC URL (from the official source)
Chain ID (e.g., 42161)
Currency Symbol (e.g., ETH)
Block Explorer URL (optional but critical for verification)



High traffic often causes public RPC nodes to fail. Switch to a private RPC endpoint from services like Infura, Alchemy, or QuickNode for consistent performance and higher rate limits.


Clear the application's cached network data. Outdated information, like an old RPC URL saved from a previous session, will override new settings and cause persistent failures.


Confirm your device's firewall or security software isn't blocking connections to the RPC node's specific port. This is a common, overlooked issue on corporate or restricted networks.


Cross-check the configured chain ID with the network's current value using a block explorer. Developers sometimes update these IDs on testnets, causing a mismatch that halts all transactions and balance queries.


For custom or local networks, ensure the node is running and accessible. Use command-line tools like `curl` to test the RPC endpoint directly before attempting to add it to your interface.

Balance Display and Token Visibility Issues

First, manually add the token's contract address to your asset list. Networks like Solana, Ethereum, or BNB Smart Chain require the precise address, which you must obtain from a reliable block explorer. If the balance appears as zero for a token you own, force a refresh of your portfolio view and verify you are connected to the correct blockchain; an incorrect network is the most frequent cause of missing funds.


Persistent incorrect figures often stem from outdated RPC node data. Change your custom RPC endpoint to a more responsive public one or, for better synchronization, clear your cache. For NFTs or newer tokens, confirm the digital asset standard is supported–your interface may not automatically recognize experimental or proprietary token types without explicit configuration in its settings menu.

Updating or Reinstalling the Coin98 Extension

Manually check for a newer version in your browser's add-on management page; automatic updates can sometimes fail or be delayed by days.


If the tool malfunctions, a complete refresh often resolves corrupted local data. First, export your private keys or seed phrase to a secure location–this step is non-negotiable for asset safety. Then, remove the add-on from your browser and restart the application before fetching a fresh copy from the official store.


The installation process requires specific permissions. After adding it, you will typically need to:Grant access to view and interact with website data.Create a new vault or import your existing one using the recovered credentials.Re-add custom network RPC details if you operated on non-default chains.


Persistent errors post-reinstallation might stem from browser cache conflicts. Clear your cached images and files for the last 24 hours, disable other blockchain utilities to check for conflicts, and ensure your operating system and browser are patched to their latest stable builds.

Q&A:
I installed the Coin98 extension but the icon isn't showing in my browser toolbar. How do I fix this?

Sometimes browser extensions are installed but not pinned to the toolbar. In Chrome, Edge, or Brave, click the puzzle piece extension icon. Find "Coin98 Wallet" in the list. Click the pin icon next to it. If you don't see it in the list, the installation might have failed. Go to your browser's extension management page (chrome://extensions, for example). Check if Coin98 is listed and enabled. If it's there but disabled, enable it. If it's not there, return to the Chrome Web Store and install it again.

After setup, my Coin98 wallet says "No accounts found" or won't import my existing wallet. What's wrong?

This usually points to an issue with your recovery phrase or private key. Double-check every word of your 12 or 24-word seed phrase. Ensure there are no typos, extra spaces, or incorrect word order. The phrase is case-sensitive and must be entered exactly. If importing via private key, verify you've copied the entire key correctly. Also, confirm you've selected the correct derivation path for the blockchain network you intend to use. Using the wrong path can generate a different set of addresses. Try the process one more time, typing carefully. If the problem continues, the phrase or key might be for a different wallet or could be incorrect.

Why does the Coin98 extension keep disconnecting from websites like PancakeSwap?

Browser wallets need to maintain an active connection to interact with decentralized apps. This disconnection often happens due to browser memory management or conflicts. First, try refreshing the website page. If that fails, manually reconnect the wallet within the website's interface—look for a "Connect Wallet" button. Ensure you've selected the right account within Coin98 if you have multiple. Another common fix is to restart your browser. For a longer-term solution, check for updates to the Coin98 extension, as newer versions often improve connection stability. Also, review other installed extensions; security or ad-blocking tools can sometimes interfere with wallet connections.

I'm trying to send tokens but the transaction keeps failing or is stuck. What can I do?

Failed transactions typically relate to network conditions or wallet settings. First, verify you have enough of the native cryptocurrency (like BNB for BSC, or ETH for Ethereum) to pay for the transaction fee. Insufficient gas funds will cause all transactions to fail. Next, check the current network congestion; high traffic can lead to timeouts. You might need to adjust the gas fee. In Coin98, when confirming a transaction, you can often choose a "Fast" option or manually set a higher gas price. If a transaction is stuck, do not submit multiple attempts. You can try to speed up the original transaction if the network supports it, or wait for it to eventually drop from the mempool before trying again with a higher fee.
Remy Froissart, CNRS

Outils pour utilisateurs

Outils du site

Outils de la page
