This article outlines the various types of 'execution reverted' errors and provides troubleshooting guidance for each.
My transaction failed with an [execution reverted] error
Your transaction may fail in certain situations, displaying an [execution reverted] error in the block explorer. This error commonly occurs with transactions involving smart contract interactions, such as sending ERC20 or BEP20 tokens or NFTs, or utilizing decentralized apps (dapps) on blockchains that employ the Ethereum Virtual Machine (EVM), including Ethereum (ETH), Polygon (MATIC), Arbitrum (ARB), Optimism (OP), Binance Smart Chain (BSC), and others.
The [execution reverted] error indicates a transaction that couldn't be executed due to unmet conditions in the underlying smart contract. Essentially, the Ethereum Virtual Machine (EVM)—the engine powering smart contract execution—reverts the state to its condition before the transaction attempt.
It's important to understand that even though the transaction was only partially executed before being reverted, it will still consume network fees (gas), as the network compensates miners or validators for processing the failed transaction.
There are multiple reasons why a transaction might fail with an [execution reverted] error, often arising when a transaction violates the logic set within the contract. If you encounter an execution reverted error, consider the following:
- Some crypto exchanges (such as Binance, Kraken, Coinbase, etc) use smart contracts to facilitate deposits of ETH and ERC20 tokens. If you're encountering an [execution reverted] error when depositing to an exchange, please consider reaching out to the exchange support team's for assistance.
- Similarly, if you come across an [execution reverted] error while engaging with a decentralized application (dApp), reaching out to the team or community behind the dApp's smart contract can offer the necessary support and guidance