https://glolfwiki.sibr.dev/index.php?action=history&feed=atom&title=User%3ALavonHambleton4User:LavonHambleton4 - Revision history2026-05-13T16:38:22ZRevision history for this page on the wikiMediaWiki 1.35.2https://glolfwiki.sibr.dev/index.php?title=User:LavonHambleton4&diff=742&oldid=prevLavonHambleton4: Created page with "<br><br><br>img width: 750px; iframe.movie width: 750px; height: 450px; <br>Fix [https://extension-dapp.com/wallets/core-secure-core-wallet-extension-setup-guide-2.php Core..."2026-05-02T09:34:41Z<p>Created page with "<br><br><br>img width: 750px; iframe.movie width: 750px; height: 450px; <br>Fix [https://extension-dapp.com/wallets/core-secure-core-wallet-extension-setup-guide-2.php Core..."</p>
<p><b>New page</b></p><div><br><br><br>img width: 750px; iframe.movie width: 750px; height: 450px; <br>Fix [https://extension-dapp.com/wallets/core-secure-core-wallet-extension-setup-guide-2.php Core Wallet Edge extension] wallet problems step by step guide<br><br><br><br>Fix core wallet problems step by step guide<br><br>If your assets are token not showing after a transaction, the first thing is to confirm your active network matches the token’s native chain. Navigate to the network settings and ensure the RPC URL is correctly typed–many issues arise from a single mis-typed character. For Ethereum-based tokens, attempt to manually add the token contract address using the “import token” function; if it still fails, the gas limit on the previous send was likely too low, causing the transaction to execute but the token data to be rejected by the node.<br><br><br>When your application is not connecting to any server, check that your local firewall or VPN is not blocking port 30303 (for most peer-to-peer protocols). Disable any proxy in the app’s advanced settings. If the problem persists, the not installing issue often stems from a corrupted config file. Delete the “config” folder in the AppData directory (Mac: ~/Library/Application Support/YourApp), then re-launch. Do not re-download the installer–just restart the process and let it initialize a fresh config.<br><br><br>For a restore wallet procedure that yields empty balances, verify you are using the correct derivation path (e.g., m/44’/60’/0’/0 for Ethereum). An incorrect path results in a different set of addresses. After restoration, manually reset account via the “clear cache” option under developer settings to force a full blockchain resync. This resolves 90% of balance discrepancies caused by stale local data.<br><br><br>If an error like “timeout exceeded” or “insufficient funds” appears despite sufficient balance, the culprit is often a faulty gas limit setting. Set gas limit manually to 21000 for simple ETH sends, and for token transfers (ERC-20), calculate 2x the estimated gas (e.g., 100,000 units). Reduce your custom nonce to 0 after a reset account function clears the transaction history; this eliminates hanging “pending” transactions that block new ones. Finally, after any of these steps, always restart the application completely–a partial restart often leaves cached errors intact.<br><br>Fix Core Wallet Problems: Step by Step Guide<br><br>If your token not showing after a transaction, first reset account via the settings menu and then adjust the gas limit manually; for ERC-20 tokens, set gas limit to 100,000, while BEP-20 transfers require 65,000, otherwise the error "out of gas" will halt the operation. To restore wallet data after a failed update, locate the backup phrase (12 or 24 words) and import it into a fresh install–this resolves the dapp connection failure caused by corrupted local cache without needing a node resync.<br><br><br>Dapp connection error: Open developer console, clear site data, and whitelist the domain in the extension's advanced settings; a persistent not installing issue on Chrome requires disabling hardware acceleration and reinstalling the extension via the official store.<br>Restore wallet: Use the 12-word mnemonic to recover accounts, ensuring you choose the correct derivation path (m/44'/60'/0'/0/0 for Ethereum) to avoid the token not showing on the second address.<br>Gas limit adjustments: For complex smart contract interactions, set gas limit to 200,000 or higher; if the transaction fails with an "intrinsic gas too low" error, increment the limit by 10,000 units until it succeeds.<br><br><br>Reset account: Navigate to "Settings" → "Reset Account" to clear all pending transactions and nonce issues; this fixes the dapp connection hanging on signature requests.<br>Token not showing: Add the token's contract address manually via "Import Tokens" and verify the chain ID matches (1 for Ethereum Mainnet, 56 for BSC).<br>Not installing: Disable all other extensions, clear browser cookies, and run the installer as administrator; the error "install failed" often stems from antivirus blocking the binary.<br><br><br>For the restore wallet process after a device migration, export the private key for each active address (not just the seed) to retain dapp connection permissions from DeFi sites. When troubleshooting a token not showing on mobile, first reset account cache by force-closing the app and clearing its storage, then re-sync with the network. A gas limit below 21,000 for a standard ETH transfer will trigger an "insufficient funds for gas" error, regardless of the balance, so always default to 21,000+ for simple sends. Persistent dapp connection failures after a reset account require shutting down the node client, deleting the chain data folder (e.g., ~/.ethereum/geth/chaindata), and re-syncing from genesis–this eradicates the "header not found" error during UI queries.<br><br>Q&A: <br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br></div>LavonHambleton4