You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on #1475 I found out that in the Ethereum JSON-RPC Specification for eth_getTransactionByBlockHashAndIndex method in the response for 1559 and 2930 transaction yParity and accessLists are returned. Since, we want to conform to the Ethereum specs, we need to introduce these changes to our API.
N.B Same thing happens for eth_getTransactionByBlockNumberAndIndex and should be fixed
Steps to reproduce
Send request for eth_getTransactionByBlockHashAndIndex passing either 1559 or 2930 transaction
Additional context
No response
Hedera network
other
Version
0.30.0
Operating system
None
The text was updated successfully, but these errors were encountered:
Description
While working on #1475 I found out that in the Ethereum JSON-RPC Specification for eth_getTransactionByBlockHashAndIndex method in the response for 1559 and 2930 transaction yParity and accessLists are returned. Since, we want to conform to the Ethereum specs, we need to introduce these changes to our API.
N.B Same thing happens for eth_getTransactionByBlockNumberAndIndex and should be fixed
Steps to reproduce
Additional context
No response
Hedera network
other
Version
0.30.0
Operating system
None
The text was updated successfully, but these errors were encountered: