1.Connection and wallet
| Symptom | Likely cause | Fix |
|---|---|---|
| Wallet says the chain ID does not match | The RPC URL belongs to a different network than the chain ID you entered | Use the values from the network table and check eth_chainId |
| Wallet cannot add the network | Missing or malformed fields in wallet_addEthereumChain | Provide a hex chain ID, an HTTPS RPC URL and a currency with 18 decimals |
| Requests time out or return 429 | You hit the public rate limit | Slow down, cache responses or use a dedicated endpoint |
| Transaction shows as pending forever | The fee is too low or an earlier nonce is stuck | Resend with higher fees or replace the pending transaction with the same nonce |
2.Deployment
| Error | Likely cause | Fix |
|---|---|---|
| insufficient funds for gas | The deployer has too little native currency | Fund the account from the faucet on testnet |
| nonce too low | A transaction with this nonce was already mined | Refresh the nonce, or reset your wallet account activity |
| invalid opcode or deployment reverts with no reason | Bytecode compiled for a newer EVM version than the network supports | Lower evm_version in your compiler settings and redeploy |
| max code size exceeded | The contract is larger than the size limit | Enable the optimizer, split into libraries or contracts, or remove unused code |
| intrinsic gas too low | The gas limit was set manually and is too small | Let the tool estimate gas |
| replacement transaction underpriced | A second transaction reused a nonce without a higher fee | Raise the fee by at least the minimum increase required |
Contract size limit on this network: [contract size limit]. Supported EVM version: [EVM version].
3.Verification
Verification succeeds only when the explorer can reproduce your exact bytecode. If it fails, compare each of these with your deployment:
- Compiler version, including the patch number.
- Optimizer setting and number of runs.
- EVM version.
- Linked library addresses.
- Constructor arguments, ABI-encoded exactly as deployed.
- Imported file paths and remappings. Flatten the source if the explorer cannot resolve imports.
- The metadata hash setting. Deploy and verify with the same value.
4.Contract calls
| Symptom | Likely cause | Fix |
|---|---|---|
| Call reverts with no message | A require without a reason, an unsupported opcode or a wrong address | Run the call in a Foundry fork test with traces, and confirm the address has code |
| Call returns 0x | The address has no contract on this chain | Check cast code and that you are on the right network |
| Signature is rejected on-chain | Wrong chain ID, contract address, nonce or deadline in the signed data | Rebuild the EIP-712 domain from the live chain |
| eth_getLogs returns an error | The block range is too large | Query in smaller ranges |
| Estimated gas is much lower than needed | The call depends on state that changes before the transaction is mined | Add a margin to the estimate and test under load |
5.Still stuck
When you ask for help, include the chain ID, the transaction hash, the contract address, the compiler version and settings and the exact error text. Developer support: [developer support contact].
Highlighted items in square brackets are network values that are confirmed and published before the public testnet. Code samples are for learning and are not audited. Have any contract that will hold real value reviewed before launch. The latest version is always on this page, and a PDF copy is available above.