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
Stateless execution is the idea of not needing to maintain a state database when doing execution. A witness can be sent over p2p that includes a commitment to each state access can be used to populate an in memory memory state db during execution and a comparison to the post state state root in the block header can guarantee that the correct.
It would be nice to have a stateless derivation pipeline, where we no longer need to observe all L1 transactions/logs and instead include witnesses to an L1 header chain to populate the derivation pipeline. This idea has been explored with logs in #330 but has not yet been fully explored for batches. We could use a similar nonce idea in the batch serialization to enable this. It is also possible it could be done by turning the batch inbox into a very simple contract that simple increments a nonce and/or emits an event with metadata about the batch itself.
This would be a good improvement to the proof programs, as it would remove a lot of work iterating over blocks during the proof, and we could just include the data with witnesses instead.
The text was updated successfully, but these errors were encountered:
Stateless execution is the idea of not needing to maintain a state database when doing execution. A witness can be sent over p2p that includes a commitment to each state access can be used to populate an in memory memory state db during execution and a comparison to the post state state root in the block header can guarantee that the correct.
It would be nice to have a stateless derivation pipeline, where we no longer need to observe all L1 transactions/logs and instead include witnesses to an L1 header chain to populate the derivation pipeline. This idea has been explored with logs in #330 but has not yet been fully explored for batches. We could use a similar nonce idea in the batch serialization to enable this. It is also possible it could be done by turning the batch inbox into a very simple contract that simple increments a nonce and/or emits an event with metadata about the batch itself.
This would be a good improvement to the proof programs, as it would remove a lot of work iterating over blocks during the proof, and we could just include the data with witnesses instead.
The text was updated successfully, but these errors were encountered: