Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Mesh Wiki
Search
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
User:KarinaOld30
User page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
User contributions
Logs
View user groups
Special pages
Page information
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
<br><br><br>img width: 750px; iframe.movie width: 750px; height: 450px; <br>Fix [https://extension-wallet.org/wallet-core-setup.php Core Wallet setup guide] wallet problems step by step guide<br><br><br><br>Fix core wallet problems step by step guide<br><br>If your token not showing in the interface, first verify the contract address. A mismatch between the asset’s contract address and the one entered into the interface causes 90% of display failures. Open the block explorer for the network you are using, locate the token’s official contract, copy it, and add it manually. If the token not showing persists, clear the application cache and resync the blockchain data – this flushes corrupted ledger entries that hide balances.<br><br><br>For a failed dApp connection, terminate all browser sessions and the local client. Restart the software and ensure the dApp URL uses HTTPS and the correct chain ID. A mismatch in network ID (e.g., Ethereum Mainnet vs. RPC endpoint set to BNB Smart Chain) blocks the handshake. Manually set the network ID in the settings to match the dApp’s required chain. If the dApp connection still drops, disable any VPN or proxy, as these reroute traffic away from the correct node.<br><br><br>When you need to restore wallet access and the phrase is known, use a different client or version to validate the seed. Enter the 12 or 24 words in the exact order, checking for uppercase or lowercase discrepancies. During the restore wallet process, if the software stalls on “restoring,” the node may be behind the network tip. Wait for it to sync completely – this can take 30 minutes on a slow connection. Do not interrupt the restore wallet procedure midway, as partial state files cause missing addresses.<br><br><br>A transaction that fails due to gas limit being too low needs immediate adjustment. Increase the gas limit by 20,000 above the estimated usage for simple sends, or by 100,000 for contract interactions. If the error reads “out of gas,” the gas limit was set too low. Conversely, if the error shows “intrinsic gas too low,” the limit is below the minimum 21,000. Always set the gas limit manually after the estimate, not the gas price, to avoid not installing the transaction on chain.<br><br><br>If the application is not installing, check that the installer file is not corrupted. Verify the SHA-256 hash against the official release. A not installing error often comes from insufficient disk space – require at least 10GB free for blockchain data. If the issue is not connecting to the network, diagnose the port status. The default port 8333 for Bitcoin-based chains or 8545 for Ethereum must be open outbound. Use the software’s diagnostic log to confirm if the node finds peers; if zero peers appear, the network is blocked by a firewall or ISP restriction.<br><br>Fix Core Wallet Problems Step by Step Guide<br><br>If a token not showing after a transfer, open the asset list and manually add the contract address for the specific chain (e.g., BSC or Polygon). For persistent error messages during synchronization, clear the app cache via device settings, force stop the application, and relaunch it; if the issue persists, check your node provider endpoint for rate limiting or switch to a public RPC like https://bsc-dataseed.binance.org. When a dapp connection fails, revoke the session from the app’s connected sites list, close the browser tab, re-initialize the link by scanning the QR code again, and ensure the dapp’s network matches your active chain (mainnet vs. testnet). For the app not installing, verify your device OS version meets the minimum requirement (iOS 14+ or Android 8+), free up at least 500MB of storage, disable any VPN temporarily, and download the APK/IPA only from the official site to avoid corrupt files. If the app is not connecting to the blockchain, confirm your internet stability by pinging 8.8.8.8, then manually set a custom network with a high gas limit (e.g., 300,000 for complex swaps) to avoid transaction rejections; retry after 30 seconds.<br><br><br>If you need to restore wallet access due to a lost device, obtain your 12-word secret phrase–typed exactly as given, with spaces and lowercase–and install the application on a new device; during the recovery screen, select "Import from Seed" and enter the phrase character by character, ignoring any auto-suggestions. After restoration, re-add custom tokens by contract address, then check the blockchain explorer (like Etherscan or BscScan) to confirm the token not showing issue is resolved; if balances remain zero, update the gas limit to 210,000 for standard transfers and resend the transaction with a higher nonce (e.g., +1) to override stuck errors. For dapp connection problems post-recovery, revoke old permissions in the app settings, re-approve the session via the dapp’s login modal, and ensure your network ID (e.g., 56 for BSC) matches; if the error "insufficient funds for gas" appears, reduce the gas limit to 100,000 for simple approvals or top up your native chain token (BNB, MATIC, ETH) by at least $2 worth. When the app not installing still occurs, turn off all ad blockers and download via a cellular hotspot if Wi-Fi fails; as a final resort, use a wired USB installation on Android via ADB commands–only if you are comfortable with developer tools. If the wallet remains not connecting after three attempts, switch your DNS to Cloudflare (1.1.1.1) and reboot your router, as ISP-level throttling often triggers false connection errors.<br><br>Q&A: <br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
Summary:
Please note that all contributions to Mesh Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Toggle limited content width