feat: store log of archives in rollup contract #7615
Assignees
Comments
LHerskind
added a commit
that referenced
this issue
Jul 31, 2024
Fixes #7615. Adds a list of "BlockLog"s what we have within the 🐢 team talked about just as log for more generic consensus notation, and then have two values to address whereto the pending and the proven is accounted for. Add extra requirements to the `submitProof` function to ensure that proofs are actually linked to the blocks that are in the pending log. If all constraints are passed, will mark the block as proven (but not instantly move the tip forward). Introduce a `progressState` function which we execute at every proof submission that will try to progress the proven tip as far as possible (as long as the next block is proven we continue). This allow us to deal with non-sequential proving. - Also renames the fixtures to be block 1 and 2 instead of 0, 1 as it makes it much easier to reason about when the genesis block is actually already in the chain. - Changed a few wrongly ordered error messages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will allow us to keep track of the current tips of the "proven" and "pending" chains/logs.
As part of this issue we will store references into the list that get updated when we process pending blocks and their respective proofs.
We will also need to handle non-sequential proofs. see more
The text was updated successfully, but these errors were encountered: