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.

Sign up for GitHub

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

Jump to bottom

Return yParity from eth_getBlockByNumber #8686

Closed
quickchase opened this issue Nov 9, 2023 · 1 comment · Fixed by #9574
Closed

Return yParity from eth_getBlockByNumber #8686

quickchase opened this issue Nov 9, 2023 · 1 comment · Fixed by #9574

Comments

@quickchase
Copy link
Contributor

System information

Erigon version: v2.53.4

Chain/Network: Ethereum Mainnet

Expected behaviour

return yParity in the output of eth_getBlockByNumber

Actual behaviour

yParity key missing in the output of eth_getBlockByNumber

Steps to reproduce the behaviour

Send the following JSON-RPC request to an Erigon node and then either a Geth, Reth, or Nethermind Node, and compare the outputs:

{"method":"eth_getBlockByNumber","params":["0x10b7cfb",true],"id":1,"jsonrpc":"2.0"}

Geth, Reth, and Nethermind include a field called yParity in the output. Erigon does not.
@MRabenda
Copy link

MRabenda commented Feb 1, 2024

Hey,

@0xKrishna is there a chance that someone will support here?

@shohamc1 shohamc1 linked a pull request Mar 4, 2024 that will close this issue
rpc: Use yParity for non-legacy transactions #9574
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

rpc: Use yParity for non-legacy transactions erigontech/erigon
2 participants
@quickchase @MRabenda