🛠️Common Error Troubleshooting

Below, common issues are categorized by scenario, providing quick troubleshooting steps and solutions. For urgent issues, please check this page first. If the problem persists, please submit a support ticket or seek assistance in our Official Telegram Community.

⚠️ Important: Before performing any "Reset" or "Remove" operations, please ensure you have a valid backup of your Seed Phrase or Private Key! Any operational error may result in permanent asset loss.

1) Wallet Connection Issues

Symptoms: DApp fails to connect to the wallet / Authorization pop-up does not appear.

Troubleshooting Steps:

• Ensure your wallet is unlocked and running in the correct browser (or mobile app).

• Verify you are connected to the correct network (check the network dropdown at the top of MetaMask).

• Restart the browser extension or mobile app. If the issue persists, try switching the RPC endpoint (use an alternative public node).

• If using a browser extension, clear the page cache or try accessing the site via Incognito Mode or a different browser.

• Check if any ad blockers or privacy extensions are blocking the pop-up (disable them and retry).

2) Transaction Failed / Revert

Symptoms: The transaction is included in a block but the status is Failed (Reverted), showing a "revert" message or a specific error description.

Troubleshooting Steps:

• Check the specific reason for the failure on a Block Explorer (it often displays a specific revert string or error message).

• Verify your input parameters: Destination Address, Amount, and Contract Function Name.

• For ERC-20 transfers: Ensure the sender has Approved a sufficient allowance for the contract.

• For Contract Interactions: Verify the contract logic restrictions (e.g., Whitelists, Minimum Balance requirements, Paused state, etc.). Contact the developer or check the official documentation.

• For Token Creation/Deployment: Ensure the initialization parameters and Constructor arguments are correct.

Solutions:

• Testnet First: Try to reproduce the issue on a Testnet (Strongly Recommended).

• Allowance Issues: If the error is related to allowance, call the approve function first, then execute the transfer or swap.

• Contract Logic: If the failure is caused by the contract's internal logic, you must follow the contract's specific requirements or wait for a developer fix.

3) Insufficient Gas / Gas Estimation Failed

Symptoms: Transaction rejected ("insufficient funds"), Gas estimation failed, or the transaction remains stuck in "Pending."

Troubleshooting Steps:

• Check Native Balance: Ensure your account holds sufficient Native Tokens (the chain's gas token, e.g., ETH, BNB, OKB, XPL) to cover fees. Do not confuse this with the balance of the token you are trying to transfer.

• Gas Abstraction: For chains that support gas delegation or paying gas with stablecoins, verify if a tiny amount of the native token is still required as a base fee.

• Stuck Transactions: If a transaction has been Pending for too long, use the "Speed Up" feature in your wallet. Alternatively, "Cancel" it by sending a 0-value transaction with the same Nonce but a higher Gas fee.

• RPC Issues: If the wallet cannot estimate Gas, try switching your RPC endpoint (temporarily switch to Infura, Alchemy, or another public node) and retry.

• Complex Interactions: If estimation fails frequently, it may be due to RPC timeouts caused by complex contract logic. We recommend using a Paid Node or breaking the contract interaction into multiple, simpler steps.

4) Transaction Stuck in Pending

Symptoms: The transaction remains in a "Pending" state indefinitely, neither failing nor confirming.

Troubleshooting Steps:

• Check Gas Price: View the transaction on a Block Explorer and compare your Gas Price with the current network average. If it is too low, miners will not prioritize it.

• Speed Up: If the Gas Price is too low, use the "Speed Up" feature in your wallet to re-broadcast the transaction with a higher fee. In advanced wallets, this is done by sending a "Replacement Transaction" (same Nonce, higher fee).

• Cancel Transaction: To cancel, send a new transaction with the same Nonce and a higher Gas Price, but with 0 value (essentially a self-transfer or empty transaction).

  Note: Manually managing Nonces carries risk. Ensure your Seed Phrase is backed up before attempting this.

• RPC Sync: If the issue stems from an RPC Node being out of sync, try switching to a different RPC endpoint and checking the status again.

5) Token Balance Not Visible / Contract Unverified

Symptoms: The transaction status is "Success," but the token balance does not appear in the wallet, or the contract shows as "Unverified" on the Block Explorer.

Troubleshooting Steps:

• Check Network: Verify you are viewing the balance on the correct network (tokens are sometimes accidentally sent to a different chain).

• Import Token: For new tokens, you often need to manually "Import Token" or "Add Custom Token" in your wallet using the Contract Address.

• Contract Verification: Search the Contract Address on the Block Explorer (Etherscan, BaseScan, BscScan, PlasmaScan). If it shows as unverified (Bytecode only), contact the issuer or follow the explorer's instructions to Verify and Publish Source Code.

• On-Chain Confirmation: If the transaction status is "Success" and the logs contain a Transfer event, the funds have arrived on-chain. The issue is simply that the wallet UI is not reading the token's metadata automatically.

Solutions:

• Manually Add Token: In your wallet settings, input the Contract Address and Decimals to make the balance visible.

• For Developers: We strongly recommend verifying your contract source code on the Block Explorer to build user trust and ensure correct metadata display.

以下是符合 Web3 文档规范的英文翻译：

6) Token Approvals (Approve) & Security Risks

Symptoms: You cannot revoke permissions after approving a contract, or you are concerned about potential asset theft.

Troubleshooting & Best Practices:

• Revoke Tools: Use Revoke.cash or Etherscan Token Approvals to review and revoke allowances that are set too high or are no longer in use.

• Limit Exposure: Do not grant "Unlimited" approval to unfamiliar contracts. Always prioritize setting a Custom Spending Cap (the exact amount required) or a one-time approval.

• Regular Audits: Periodically check your active approval list and revoke any high-risk authorizations immediately.

7) "Network Mismatch" or Chain Parameter Errors

Symptoms: MetaMask displays a "Connected to Wrong Network" error, or a transaction fails due to a Chain ID mismatch.

Troubleshooting Steps:

• Verify Settings: Check your wallet's network settings to ensure the RPC URL and Chain ID match the chain you intend to use (refer to the SlerfTools Chain Parameters page).

• Custom RPCs: If using a custom RPC, ensure the input RPC URL, Chain ID, and Currency Symbol match each other correctly.

• New Chain Requirements: For newer chains (e.g., Plasma, X Layer), double-check that you hold the correct Native Token for Gas (e.g., OKB, XPL).

8) Hardware Wallets (Ledger/Trezor) Common Issues

Symptoms: Stuck on "Waiting for Signature" / Device fails to detect the signature request.

Troubleshooting Steps:

• Update Firmware: Ensure both your hardware wallet's Firmware and the management app (e.g., Ledger Live) are updated to the latest version.

• Connection Bridge: When connecting, ensure you are using the correct connection method (e.g., enabling "WebHID" in MetaMask or keeping Ledger Live open if required by the bridge).

• Verify Details: If the signature is rejected, carefully check the transaction details displayed on the physical device screen (Amount, Recipient Address, Chain) to ensure they match your request.

• Blind Signing: Complex contract interactions often require enabling "Blind Signing" (or "Contract Data") in the hardware wallet's settings. Please read the prompts on the device carefully.

9) Quick Self-Help Commands (Advanced Users)

• Switch RPC: Go to your wallet's network settings and add/switch to a high-stability node (e.g., Infura, Alchemy, QuickNode).

• Reset MetaMask Account: This action clears the local transaction history (stuck pending txs) but does not delete your assets.

  • Path: Settings → Advanced → Reset Account.

  • Warning: Although this is generally safe, always ensure your Seed Phrase is backed up before performing this action.

• Check Nonce & Replace Transaction: Use a Block Explorer to identify your account's latest confirmed Nonce. Send a new transaction with the same Nonce (and higher gas) to overwrite the old, stuck transaction.

---

⚠️ Note: When using SlerfTools, 90% of issues are caused by Wallet Configuration or Network Connection problems.

Operation Details:

• Refresh the page + Switch networks.

• Clear Wallet Cache (MetaMask: Settings > Advanced > Clear activity tab data).

• Check the Tx Hash status on the Block Explorer.

---

📌 Error List & Solutions

Error Message	Cause	Solution
Out of Gas	Gas Limit too low	Manually increase Gas Limit to 500k+. SlerfTools uses a safe default value.
Nonce Too Low/High	Nonce Conflict	Wait for the previous transaction to confirm, or manually set the next Nonce (check Block Explorer).
Insufficient Funds	Insufficient Balance	Ensure you hold the Gas Token (BNB/ETH/OKB) and reserve at least 0.1 units.
Replacement Transaction	Duplicate Signature	Cancel the previous transaction, or Speed Up (increase Priority Fee).
RPC Error / Network Not Found	RPC Failure	Switch to an alternative RPC list.
User Rejected	Signature Rejected	Verify the pop-up details are correct, then reconnect your wallet.
Contract Deployment Failed	Contract Code Issue	Check parameters (Total Supply > 0, no special characters). Verify on Testnet first.
Low Gas Price	Tip too low	Increase Priority Fee to 1 Gwei+.
Execution Reverted	Contract Logic Error	Check the Tx details. Commonly caused by a non-existent LP Pool.
MetaMask Stuck	Gas Estimation Bug	Enable "Advanced Gas Controls" and set the fees manually.

Still stuck? 👉 Join our official Telegram group and share a screenshot for help.