When a token not showing in your interface, verify the token contract address on a block explorer like Etherscan. Missing tokens usually appear because the asset’s smart contract lacks an import procedure for the custom token list. Manually add the contract address, decimal count, and symbol. If the balance remains zero, your transaction history may show a restore wallet failure–always re-import from your seed phrase rather than relying on partial backup files.

A dapp connection refusal often stems from Web3 provider version mismatch. Disable any outdated browser extensions, clear cached site data, and approve the wallet permission prompt again. For persistent error code -32000, increase the default gas limit from 21,000 to 60,000 for complex contract calls. If the interface shows not installing on your mobile device, liberate at least 500 MB of storage, toggle airplane mode, and attempt installation from a direct APK download rather than auto-update.

Fix Core Wallet Problems: Practical Steps Guide

If your application is not connecting, verify your internet firewall isn’t blocking port 8545 or 30303. For desktop clients, switch your network provider from automatic to a specific endpoint like Cloudflare (1.1.1.1) or Google (8.8.8.8). A static DNS assignment resolves 84% of persistent connection failures without altering your node configuration.

When a specific token not showing, you must manually import its contract address. Navigate to the token list, select “custom token,” then paste the correct contract hash from a verified block explorer like Etherscan. Ensure the token hasn’t been deprecated–check for a recent transaction timestamp on the contract. If the balance remains zero despite a confirmed transfer, your node likely lacks the necessary block data; perform a full rescan starting from the block height of the transaction.

Transaction failures due to gas limit usually stem from underestimating intrinsic costs. For standard ERC-20 transfers, set the gas limit to 60,000–this covers 21,000 base plus 40,000 for token computation. Avoid relying on automated estimates for contracts with complex logic; manually raise the limit to 150,000 and multiply the current base fee by 1.5 to guarantee inclusion. If the transaction reverts, inspect the contract on a block explorer for specific error codes like “execution reverted.”

An application not installing often indicates corrupted installer files or insufficient storage. Clear your temporary directory first, then download the latest signed binary directly from the official repository. For macOS, bypass Gatekeeper by right-clicking “Open” instead of double-clicking. If Windows Defender flags the file, temporarily disable real-time protection, install, then re-enable it–the hash mismatch should resolve. Allocate at least 10 GB of free disk space before the full node sync begins.

To reset account without losing funds, delete only the local cache files–not your keystore or mnemonic backup. On Linux, remove the `~/.ethereum/geth/chaindata` folder. After a reset, re-import your private key using the JSON keystore file. This clears stale transaction nonces and incorrect balance states. Confirm the reset succeeded by checking that the account balance matches the blockchain explorer: if mismatched by more than 3 confirmations, repeat the process with a fresh node connection.

If you must restore wallet from a seed phrase, always test the recovery on a secondary device first. Enter the 12 or 24 words in exact order with correct capitalization–BIP39 mnemonic is case-sensitive. After restoration, generate a new address and send a micro-transaction (0.001 ETH) to verify the private key derivation path (commonly m/44’/60’/0’/0). If the restored balance reads zero, you may have used a wrong derivation path; try Ledger Live legacy path (m/44’/60’/0′) or a custom index like m/44’/60’/1’/0.

1. Network: Check peer count–if below 3, your node is isolated. Force connect to a known static peer via enode URL.
2. Transaction: Replace a stuck pending transaction by sending a new one with the same nonce but 20% higher gas price.
3. Data: Corrupted block index triggers the “bad block” error; delete the `ancient` folder and restart sync from the last checkpoint.
4. Hardware: SSD usage above 80% capacity causes write amplification; migrate the data directory to a dedicated drive with 20% over-provisioning.

Q&A: