## Kona ExEx ### Goals Fully sync Kona ExEx to tip and follow the safe head. ### Why What this gets us is a validation client running on top of a reth node. Effectively a single L1 reth node can have multiple Kona ExEx's installed, validating multiple L2 chains. On top of these light consensus clients following the safe head, you could then support zk proofs. ### Out of Scope - Extend Kona ExEx to support unsafe head support through p2p or trusted sequencer communication. ### Owners [refcell](https://github.com/refcell) + [clabby](https://github.com/clabby) ### Location Inside a new `kona-exex` crate in reth [crates/examples/exex](https://github.com/paradigmxyz/reth/tree/main/examples/exex). ### Roadmap 1. Import kona-derive. 2. Instantiate a revm instance that will be used to execute the L2 payloads against to generate the state root. 3. Build the kona-derive pipeline with online providers. 5. Buffer the stream of L1 blocks from reth into the derivation pipeline. 6. Run the derivation function to produce payloads. 7. Execute the payloads on the instantiated revm instance. 9. Validate state root with a trusted rollup node url (eg sequencer). ### Outputs Kona ExEx is running in OP Labs internal infrastructure and following safe head tip. The kona-exex crate is up-to-date and merged in reth trunk.