-
Notifications
You must be signed in to change notification settings - Fork 38
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
refactor: should reject transactions which have wrong encoded data #1075
Labels
bug
Something isn't working
Comments
classicalliu
changed the title
[BUG]
[BUG] eth tx hash will changed after commit to block
Jun 8, 2023
Flouse
changed the title
[BUG] eth tx hash will changed after commit to block
refactor: should reject those transactions with r that has leading zeros
Jun 8, 2023
Flouse
changed the title
refactor: should reject those transactions with r that has leading zeros
refactor: should reject transaction which have wrong encoded data
Jun 8, 2023
Flouse
changed the title
refactor: should reject transaction which have wrong encoded data
refactor: should reject transactions which have wrong encoded data
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Describe the bug
When sending a tx with
r
that has leading zeros toeth_sendRawTransaction
, it will return a eth_tx_hash, but after the tx committed to block, the eth_tx_hash will change.The RPC
eth_sendRawTransaction
's parameter is a signed raw transaction.It's encoded with some infos contains
r
ands
, it should regard asquantity
when encoding, but when encoding with bytes type, the encoded raw tx will be changed, so it will return a wrong eth_tx_hash.Expected behavior
leading zeroes are not necessary
Should reject those transactions which have wrong encoded data (e.g. with
r
that has leading zeros).Correct Example
https://etherscan.io/tx/0x07c7388b03ab8403deeaefc551efbc632f8531f04dc9993a274dbba9bbb98cbf
References
The text was updated successfully, but these errors were encountered: