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
It would be nice to see log output from the op-node, op-geth, op-reth, etc. even on a positive outcome. It appears to me, this is only shown when tests fail.
For example I would like to see the blocks being built, to check for hints that new fork rules are actually being put into action, e.g. the withdrawals root in block headers would always be the empty root hash before activation of 'l2tol1-message-passer withdrawals root' feature. whereas after activation of the feature, the withdrawals root hash in the header is expected to be a different value for different blocks, if kurtosis is submitting the right transactions and they are being recognised by the nodes.
Based on these hints, one could dismiss the possibility that the optimism-package is causing the bugs and be certain that the bugs can be found in the client impl.
The text was updated successfully, but these errors were encountered:
It would be nice to see log output from the op-node, op-geth, op-reth, etc. even on a positive outcome. It appears to me, this is only shown when tests fail.
For example I would like to see the blocks being built, to check for hints that new fork rules are actually being put into action, e.g. the withdrawals root in block headers would always be the empty root hash before activation of 'l2tol1-message-passer withdrawals root' feature. whereas after activation of the feature, the withdrawals root hash in the header is expected to be a different value for different blocks, if kurtosis is submitting the right transactions and they are being recognised by the nodes.
Based on these hints, one could dismiss the possibility that the optimism-package is causing the bugs and be certain that the bugs can be found in the client impl.
The text was updated successfully, but these errors were encountered: