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
We are facing a similar situation as in #149 , but for eth_getTransactionReceipt. Specifically there is a schema disagreement over log.transactionHash between the ethereum execution apis and go-ethereum.
The core devs either need to make it required or geth needs to come into compliance. Either outcome is acceptable to me. But we should add it on our end.
Problem
We are facing a similar situation as in #149 , but for
eth_getTransactionReceipt
. Specifically there is a schema disagreement overlog.transactionHash
between the ethereum execution apis and go-ethereum.The ethereum execution apis do not mark that property as required https://github.com/ethereum/execution-apis/blob/main/src/schemas/receipt.json#L18.
The go-ethereum client however does mark that property as required https://github.com/ethereum/go-ethereum/blob/master/core/types/log.go#L45.
Would be great if we can include the transactionHash inside logs so that we satisfy the go-ethereum validation.
Solution
The logs are mapped here on the relay node:
hedera-json-rpc-relay/packages/relay/src/lib/eth.ts
Lines 701 to 716 in 84fffed
Alternatives
No response
The text was updated successfully, but these errors were encountered: