<!-- Need help? Refer to our contributing guidelines for additional information about making a good issue: https://github.com/ethereum-optimism/.github/blob/master/CONTRIBUTING.md --> **Describe the bug** The `rollup` RPC namespace in geth is not fully covered. The main method right now is `rollup_getInfo` The implementation is found here: https://github.com/ethereum-optimism/optimism/blob/2dd79f702403c7ee8282466a2e315ce40813060b/l2geth/internal/ethapi/api.go#L1928 There is a known bug where the L1BlockNumber that is returned is incorrect, see https://github.com/ethereum-optimism/optimism/pull/522#discussion_r617060502 **To Reproduce** Steps to reproduce the behavior: 1. Start up a replica using https://github.com/ethereum-optimism/optimism/issues/473 1. Send the RPC request `rollup_getInfo` 1. The blocknumber does not accurately match the EVM `NUMBER` opcode if a transaction were to execute at that moment **Expected behavior** All fields returned by the RPC are correct and tested
Describe the bug
The
rollupRPC namespace in geth is not fully covered. The main method right now isrollup_getInfoThe implementation is found here:
optimism/l2geth/internal/ethapi/api.go
Line 1928 in 2dd79f7
There is a known bug where the L1BlockNumber that is returned is incorrect, see #522 (comment)
To Reproduce
Steps to reproduce the behavior:
rollup_getInfoNUMBERopcode if a transaction were to execute at that momentExpected behavior
All fields returned by the RPC are correct and tested