Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From address reported by hmyv2_ and eth_ is different #4232

Closed
MaxMustermann2 opened this issue Jul 15, 2022 · 1 comment
Closed

From address reported by hmyv2_ and eth_ is different #4232

MaxMustermann2 opened this issue Jul 15, 2022 · 1 comment
Assignees

Comments

@MaxMustermann2
Copy link
Contributor

Reported by a Discord user, and probably linked to chainId since the from address of a transaction is calculated on the fly using it as an input.

from pyhmy import transaction, util
from web3 import Web3
tx_hash = '0xffa92de7c8ec1ff53d796daaf9912198617616e3bf0f85c7f10665892ea18688'
endpoint = 'https://api.harmony.one'
# uses hmyv2_getTransactionByHash internally
hmy_result = util.convert_one_to_hex( transaction.get_transaction_by_hash( tx_hash, endpoint )[ 'from' ] )
web3 = Web3( Web3.HTTPProvider( endpoint ) )
# uses eth_getTransactionByHash
eth_result = web3.eth.get_transaction( tx_hash )[ 'from' ]
print( hmy_result )
print( eth_result )
0x423E101673c796Cbeb78AA28E703478D79291Afe
0xFD51d9C108b654208789D441c57CbA5e1866dc0d

Will be replicated on localnet and fixed once the current priority work is resolved.

@adsorptionenthalpy
Copy link
Contributor

Closing as resolved.
Check here for fix:
#4581 and
#4582

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@adsorptionenthalpy @MaxMustermann2 and others