0

For example, Mana token page at Etherscan is https://etherscan.io/token/0x0f5d2fb29fb7d3cfee444a200298f468908cc942

Mana contract page at Etherscan is https://etherscan.io/address/0x0f5d2fb29fb7d3cfee444a200298f468908cc942 (same hash as above)

At the contract page the following page is claimed to be the token creation tx page https://etherscan.io/tx/0xc276acd60857b70bc986f6ccf0d2b968411b4194f02c34050f708e536d9369e9

When I query my local Erigon node using eth_getTransactionReceipt and the above creation tx hash, I see that the contractAddress field actually got a different value than the stated token hash - 0xa66d83716c7cfe425b44d0f7ef92de263468fb3d (instead of 0x0f5d2...)

Most of the tokens I checked do return the expected contractAddress.

Am I wrong to expect the contractAddress to be equal to the token address which is claimed? if not, does that mean that Etherscan is displaying wrong information?

Thanks!

1

1 Answer 1

0

Apparently it's also possible to create contracts using an internal tx with a type of CREATE or CREATE2 and that's the case for the above tokens

1
  • For readers to understand it better, add an explanation on how internal transactions using CREATE or CREATE2 can output different contract addresses.
    – DevCrypto
    Mar 5 at 12:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.