Troubleshooting | Ethereum

EthereumNetworkNotConfiguredException
The network value on an operation (or Ethereum:DefaultNetwork) doesn't match any key under Ethereum:Networks in appsettings.
Fix: confirm spelling matches exactly (case-sensitive), or add the missing entry — see Networks.

"No signing credential configured"
A write operation (transaction.send, token.transfer, contract.write, any NFT transfer/approval, wallet signing, etc.) was called without a usable credentialID.
Fix: set credentialID on the node to a vault entry of type CRYPTO_WALLET containing a PrivateKey or SeedPhrase. See Configuration.

account/history fails with INDEXER_NOT_CONFIGURED
Standard JSON-RPC has no method to list an address's past transactions — Ethereum nodes don't index by address. This operation needs a separate Etherscan-compatible indexer API that isn't wired up in this build.
Fix: none available today — see Roadmap. In the meantime, use transaction.get/transaction.receipt with hashes your workflow already tracked (e.g. from a previous transaction.send in the same run).

transaction/pending returns an error or empty results
Mempool visibility is RPC-provider-dependent — not every provider exposes a pending-transactions equivalent, especially on free-tier plans.
Fix: confirm your RPC provider supports mempool/pending-tx queries, or avoid relying on this operation and instead poll transaction.receipt for a specific known hash.

resource=contract, operation=logs returns "operation not found"
contract.logs is fully implemented in code but is not currently wired into the node's operation-routing switch, so it's unreachable through the node today.
Fix: none available today from configuration — see Roadmap. As a workaround, use contract.read/contract.multicall for current state, or pull logs from a transaction.receipt you already have the hash for, then decode with utility.decodeEventLog.

Contract call reverts unexpectedly
Most often a wrong functionName/abi pairing, wrong argument order/types in functionArgs, or a genuinely-reverting call (insufficient balance/allowance, access control, paused contract).
Fix: run the same call through contract.simulate first — see Contract Operations — to get the revert reason without spending gas. Double-check the ABI fragment matches the deployed contract exactly.

token/mint or nft/mint reverts
Minting is not part of the ERC-20/ERC-721 standards. These operations assume a common OpenZeppelin-style mint(address,uint256)/safeMint(...) shape and will revert against any token/collection that doesn't implement a matching function or that restricts minting to a specific role your signing key doesn't have.
Fix: confirm the target contract actually exposes a public/permissioned mint function your credential's address can call; override functionName if it uses a different name.

nft/listOwnedTokens fails with NOT_SUPPORTED
The contract doesn't implement the ERC-721 Enumerable extension (interface ID 0x780e9d63) — many popular collections skip it to save gas on mint.
Fix: check first with contract.detectStandards; if Enumerable isn't supported, there's no reliable way to list owned tokens without an off-chain indexer.

RPC provider rate limiting (HTTP 429)
Alchemy/Infura/QuickNode free-tier plans cap requests per second/month. EthereumRateLimitHandler retries automatically, but sustained heavy use (e.g. a large block.list count, or a tight polling loop) can still exceed a plan's hard cap.
Fix: reduce block.list's count, back off polling intervals, or upgrade the provider plan / route the network to a dedicated RpcUrlCredentialId with higher limits.

ENS operations return not-found for a name that resolves fine on etherscan.io/app.ens.domains
Either the wrong network was targeted (ENS Registry only exists at its known address on Ethereum mainnet and some testnets — not on most L2s), or the name uses a normalization/character set beyond the manual implementation's verified plain-ASCII .eth scope.
Fix: confirm network=ethereum (or the correct testnet); see ENS Operations for the implementation's known scope caveat.

account/balance or gas fields look "off by a lot" (e.g. 18 zeros too many/few)
Wei/gwei/ether unit confusion — the most common integration mistake with any Ethereum node.
Fix: remember amounts are wei by default everywhere (1 ether = 10^18 wei = 10^9 gwei) unless a format/formatDecimals field explicitly requests a formatted value. Use utility.convertUnits rather than converting by hand.