Ethereum Ethercan error: Creating many TXS tokens returns different contract addresses
The Ethercan platform has recently experienced a problem with the return of creation transactions for several tokens, including humans. This error led to confusion for both users and programmers. In this article we will arrive what the problem causes and we will provide a solution.
Problem:
API Ethercan returns various addresses of contracts for the same token, which can be misleading when working with many contracts. The problem is how API TOKEN Creation transactions supports.
case studies -OKEN mana:
Let’s take Mana as an example. According to his website at Ethercan ( the Creation -Transaction is:
`Sol
0xf1e6db9d9b7e8ff4bfedddddddddddddddd77ce55cafa93be94
However, if you try to access this address of the contract with Ethercan (https: //etherscan.io/address/…), there is an error message back:
`Text
Contract Address Error: 0x0000000000000000000000000000000000000000000000
`
This indicates that the creation transaction has not been successfully implemented.
Solution:
To solve this problem, Ethercan provides a bypass so that users can provide the address of the contract in the “Contractddress” area of the API request. In this way, the API can return the right address for the token, even if many contracts have created a token at the same time.
Here is an updated example:
Api Ethercan Request:
`Json
{
"Method": "ETH_Sendtransaction",
"Parameter": [
{
"Data": "0x0f5D2FB29FB7D3CFEE44A200298F468908C942"
}
],],
"Contract": "0x0f5d2FB29FB7D3CFEE44A200298F468908cc942" // right this address on the right right
}
What next:
1
- Check whether many contracts have not created token at the same time, as this can also lead to problems with Apiethercan.
If you follow these steps, you should be able to solve the problem and effectively restore the transaction of creating the Mana token in Ethercan.
Tips and variants:
- Check the address of the contract in the contract code or in the implementation information to check whether it is correct.
- If the problem remains, you should check the transactions or Ethereum diaries to ensure that there are no problems when creating a tokens.
- In some cases, it may be necessary to use a different API endpoint or an inquiry format to download the creation transaction.
I hope that this will help to explain all confusion caused by the return of Ethercan from various contractual attacks for the same token. If you have any further questions or doubts, you can ask yourself!