With TruffleProvider as the provider, if one uses web3.eth.getTransaction(txHash) with a valid txHash, the web3 client would complain the underlying sender address one1xxxxxx... is not a valid Ethereum address. I noticed hmy_getTransactionReceipt is overloaded and handled in a special way in truffleProvider.ts, but not hmy_getTransaction. That may be the underlying reason for the error.
A workaround is to use getTransactionByHash in @harmony-js/core/blockchain.ts, but that requires creating a separate instance for RPC call rather than using web3, which would be undesirable
With TruffleProvider as the provider, if one uses web3.eth.getTransaction(txHash) with a valid txHash, the web3 client would complain the underlying sender address
one1xxxxxx...is not a valid Ethereum address. I noticedhmy_getTransactionReceiptis overloaded and handled in a special way in truffleProvider.ts, but not hmy_getTransaction. That may be the underlying reason for the error.A workaround is to use
getTransactionByHashin@harmony-js/core/blockchain.ts, but that requires creating a separate instance for RPC call rather than using web3, which would be undesirable