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
I am wondering if this utility could be extended to identify issues such as ethereum/go-ethereum#29550 by identifying properties of interdependent RPC's and implementing them as a side-car to nodes, performing random validation against these properties as the node runs on a testnet.
For example, if one calls getTransactionReceipt the receipt should be identical to the one available in getBlockReceipts and all the transaction/block fields should be consistent. The receipt should also be able to be proven in getBlock's receipt root.
If you have any ideas or suggestions, I would be interested to get this implemented and incorporated in EF testing
The text was updated successfully, but these errors were encountered:
I am wondering if this utility could be extended to identify issues such as ethereum/go-ethereum#29550 by identifying properties of interdependent RPC's and implementing them as a side-car to nodes, performing random validation against these properties as the node runs on a testnet.
For example, if one calls
getTransactionReceipt
the receipt should be identical to the one available ingetBlockReceipts
and all the transaction/block fields should be consistent. The receipt should also be able to be proven ingetBlock
's receipt root.If you have any ideas or suggestions, I would be interested to get this implemented and incorporated in EF testing
The text was updated successfully, but these errors were encountered: