Adrian Sutton
Adrian Sutton
As log records and chain head updates are received, verify the existence of dependent logs and advance heads as appropriate.
Design and implement a way to track the chain heads for each chain. Need to at least work out how to ensure they are consistent with the log db, though...
When op-supervisor starts up, it needs to check if a reorg has happened on any of its chains that invalidates the logs it has already written. Need to think it...
Insert a stage into the fetching pipeline to identify when a reorg has occurred. Output an event down the pipeline that will rollback stages as needed (e.g. the log fetcher...
After #11024 as logs are produced from the fetching pipeline, record them to the appropriate log db for that chain, including the log and executing message.
After #11022, add a stage to the fetcher pipeline that identifies any `ExecutingMessage` logs coming from the `CrossL2Inbox` and decode them so the executing message details can be added to...
Once dispute-mon has support for reading from multiple rollup nodes (#11019), we need to expose additional metrics to support alerting when there are disagreements between nodes or some nodes failing....
`op-dispute-mon` currently uses a single `op-node` RPC endpoint to fetch output roots from (in [AgreementEnricher](https://github.com/ethereum-optimism/optimism/blob/f2e06c31b8cac95d36f2219a468244163f8bc26f/op-dispute-mon/mon/extract/agreement_enricher.go#L41-L70)). If this node is offline, out of sync or for some reason has forked off...
The memory usage of `op-challenger` is gradually increasing the longer it runs. While the rate of increase is slow and going to cause any actual issues, particularly for networks that...
The log db format doesn't currently have a way to skip more than 255 blocks without recording a log: https://github.com/ethereum-optimism/optimism/blob/f3da9a539a0789dd7f7e014cb3b1ae298c5f0cb8/op-supervisor/supervisor/backend/db/entries.go#L94-L97 We need to add support for a new event type:...