Ethereum Etherscan bug: Mana Token Creation TXs return different contract addresses
Recently, the Etherscan platform had issues returning creation transactions for several tokens, including Mana. This error caused confusion among users and developers. In this article, we will find out what is causing the problem and provide a solution.
Problem:
The Etherscan API returns different contract addresses for the same token, which can be confusing when working with multiple contracts. The problem lies in the way the API handles token creation transactions.
Mana Token Case Study:
Let’s take Mana as an example. According to the Etherscan page ( the creation transaction:
0xf1e6db9d9b7e8ff4bfeddd9cd77ce55cafa93be94
However, when you try to access this contract address on Etherscan ( an error message is returned:
Contract address error: 0x0 Here is an updated example:
EtherScan API request:
json
{
“method”: “eth_sendTransaction”,
“parameters”: [
{
“data”: “0x0f5d2fb29fb7d3cfee444a200298f468908cc942”
}
],
“contractAddress”: “0x0f5d2fb29fb7d3cfee444a200298f468908cc942” // Return this address
}
“`
What to do next:
- Check that thecontractAddress` field is specified in the API request.
- Check that multiple contracts are not creating tokens at the same time, as this can cause issues with the EtherScan API.
By following these steps, you should be able to resolve the issue and successfully receive a creation transaction for the Mana token on Etherscan.
Tips and changes:
- Be sure to check the contract address in the contract code or implementation notes to make sure it is correct.
- If the problem persists, consider checking the Ethereum blockchain transactions or records to ensure there are no issues with the token creation.
- In some cases, you may need to use a different API endpoint or request format to get the creation transaction.
I hope this helps clear up any confusion caused by Etherscan returning different contract addresses for the same token. If you have any more questions or concerns, feel free to ask!