All selectors

OpenZeppelin 5

0xec442f05: ERC20InvalidReceiver

error ERC20InvalidReceiver(address)

What it means

A transaction that reverts with the raw data 0xec442f05 hit the custom error ERC20InvalidReceiver, defined in OpenZeppelin 5. The explorer shows the hex because it does not have the contract's ABI to translate it.

The token transfer names an invalid receiver, typically the zero address. Sending tokens to the zero address burns them, so the standard blocks it unless done through an explicit burn.

How to fix it

Check the recipient address in the transaction. If a dapp filled it in, report the bug to the dapp.

Want the exact answer for your transaction?

Paste the hash and we decode the revert against the contract itself, including the values inside the error, free.

Decode my transaction

More OpenZeppelin 5 errors

0x118cdaa7OwnableUnauthorizedAccount
0x1e4fbdf7OwnableInvalidOwner
0xe450d38cERC20InsufficientBalance
0xfb8f41b2ERC20InsufficientAllowance

Every selector on this page was computed as the first 4 bytes of keccak256 of the signature shown. A selector identifies a signature exactly; on rare occasions two different signatures share one, so the transaction decoder is always the more precise answer.