Web3 New Added 12 September 2026

Web3: missing revert data in call exception (CALL_EXCEPTION)

The call failed without a reason string, which usually means there is no contract at that address on this chain rather than a failed require. A deployment address from a different network, a proxy that was never initialised, or an ABI that does not match the deployed bytecode all produce it.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# The first question is whether any code exists at the address
cast code 0xContract --rpc-url $RPC_URL | head -c 20
# 0x means nothing is deployed there on this chain

# Then whether the function selector exists in that bytecode
cast call 0xContract "totalSupply()(uint256)" --rpc-url $RPC_URL

// An ABI mismatch fails the same way: regenerate it from the deployed source
// and check the address came from the right deployment file
const c = new ethers.Contract(address, abi, provider);
console.log(await provider.getNetwork());

# A proxy returns code but forwards to an implementation that may be unset
cast storage 0xProxy 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc --rpc-url $RPC_URL

# Custom errors are revert data the ABI cannot decode, a different case
cast run 0xTxHash --rpc-url $RPC_URL

How to diagnose Web3 errors

Web3 errors are unusually terse because the EVM reports failure without explanation by default. execution reverted means a require or revert triggered. The reason string is present in the return data but most libraries discard it. Nonce errors reflect the strict sequential ordering of transactions per account, so a stuck transaction blocks every one behind it.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Simulate before sending: eth_call against the same block returns the revert reason string that a submitted transaction hides.
Use a transaction tracer (Tenderly, Foundry's cast run, or a node's debug_traceTransaction) to see the exact opcode and contract where execution reverted.
For nonce errors, query the account's pending nonce (eth_getTransactionCount with the pending tag) rather than tracking it locally.
To replace a stuck transaction, resend with the same nonce and a materially higher gas price: most nodes require at least a 10% increase.
Check the chain ID matches the network you intend. Signing for the wrong chain produces confusing rejection messages.

Tools worth reaching for

cast (Foundry)
eth_call simulation
Tenderly / block explorer tracer
debug_traceTransaction

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

docs.ethers.org ethereum.org

Related Web3 errors

See all 17 Web3 errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.