You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported here: #583 when we perfrom eth_getCode for HTS tokens, currently the result for HTS token addresses is INVALID_CONTRACT_ID as we do not return the redirect bytecode.
As described in the issue logged in the consensus node: hiero-ledger/hiero-consensus-node#3659
Although a consensus node change could be made, it will be more cost efficient (hbar cost) if the contract bytecode call to the mirror node fails to then see if it is a HTS token (checking mirror node) and then apply the proxy code to it. Similar network load, but the GetContractBytecode call will cost on the first hit if not cached.
Kalina-Todorova
changed the title
eth_getCode for that address, but currently the result for HTS token addresses is INVALID_CONTRACT_IDeth_getCode to return the redirect bytecode for HTS tokens
Oct 6, 2022
Description
As reported here: #583 when we perfrom eth_getCode for HTS tokens, currently the result for HTS token addresses is INVALID_CONTRACT_ID as we do not return the redirect bytecode.
As described in the issue logged in the consensus node: hiero-ledger/hiero-consensus-node#3659
Although a consensus node change could be made, it will be more cost efficient (hbar cost) if the contract bytecode call to the mirror node fails to then see if it is a HTS token (checking mirror node) and then apply the proxy code to it. Similar network load, but the GetContractBytecode call will cost on the first hit if not cached.
Steps to reproduce
Described in an example here: #583
Additional context
Redirect bytecode:
fefefefefefefefefefefefefefefefefefefefe
should be replaced with token addressHedera network
mainnet
Version
v0.8.0
Operating system
No response
The text was updated successfully, but these errors were encountered: