-
Notifications
You must be signed in to change notification settings - Fork 75
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
Wrong transaction receipt generated for a transfer transaction #1710
Comments
stoqnkpL
changed the title
Wrong transaction receipt generated by the Relay
Wrong transaction receipt generated by the Relay for a transfer transaction
Sep 4, 2023
stoqnkpL
changed the title
Wrong transaction receipt generated by the Relay for a transfer transaction
Wrong transaction receipt generated for a transfer transaction
Sep 4, 2023
bibitibooo1
moved this from Sprint BackLog
to In Progress
in Smart Contract Sprint Board
Sep 7, 2023
2 tasks
2 tasks
github-project-automation
bot
moved this from In Review
to Done
in Smart Contract Sprint Board
Sep 13, 2023
We need to double check if |
@Ivo-Yankov were we able to double check? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm sending a transfer to an existing account with an EVM address alias. I'm using the following code snippet:
I then get the transaction and transaction receipt through the JSON-RPC API endpoints
eth_getTransactionByHash
andeth_getTransactionReceipt
:There are several problems with the transaction and transaction receipt results:
from
field in the receipt is populated with the long-zero address, should be the alias.to
field in both the transaction and the receipt is populated with the long-zero address, should be the alias.contractAddress
field is populated with the alias of the transfer receiver account. This is wrong, this field should only be populated if the top-level call was a contract creation and should be populated with the address of the deployed contract.The text was updated successfully, but these errors were encountered: