Ethereum: Etherscan claims MANA, DEXE & REQ tokens creation tx’s return different contractAddresses, they got an issue or I miss something?

Ethereum Etherscan Error: Mana Token Creation TX Returns Different Contract Addresses

Recently, there was an issue with the Etherscan platform rolling back transactions for the creation of several tokens, including Mana. This error has led to confusion among users and developers. In this article, we will look at what is causing the issue and offer a solution.

Problem:

The Etherscan API returns different contract addresses for the same token, which can be confusing when working with multiple contracts. The issue lies in how the API handles token creation transactions.

Mana Token Case Study:

Let’s take Mana as an example. According to the Etherscan site ( the creation transaction is:

0xf1e6db9d9b7e8ff4bfeddd9cd77ce55cafa93be94

However, when you try to access this Etherscan contract address ( the error message is returned:

Contract address error: 0x0

This means that the creation transaction was not successfully deployed.

Solution:

To resolve this issue, Etherscan provides a workaround by allowing users to enter the contract address in the “contractAddress” field of the API request. This allows the API to return the correct contract address for the token, even if the token created multiple contracts at the same time.

Here is an updated example:

Ethernet API request:

{
"method": "eth_sendTransaction",
"parameters": [
{
"data": "0x0f5d2fb29fb7d3cfee444a200298f468908cc942"
}
],
"contractAddress": "0x0f5d2fb29fb7d3cfee444a200298f468908cc942" // Return this address
}

What to do next:

• Make sure the contractAddress field is specified in the API request.

• Check if multiple contracts created the token at the same time, as this can also cause issues with the Etherscan API.

Following these steps should help you resolve the issue and successfully get the Mana token creation transaction on Etherscan.

Tips and Variations:

• Be sure to check the contract address in the contract code or in the implementor notes to verify that it is correct.

• If the issue persists, consider checking the Ethereum blockchain transactions or logs to make sure there are no issues with 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 further questions or concerns, please feel free to ask!

REWARD MNEMONIC CRYPTO TRADING