Replies: 1 comment
-
I believe we are going to work on P2P communication layer between nodes, this can be how we enable communication between sequencer & prover. But i guess this solution is very plausible. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now we wait for finalized SequencerCommitments to generate a BatchProof and for a finalized BatchProof to generate a LightClientProof.
Because of that we use DA as a messaging system, not as a Data Availability layer. This leads to delays in how our subsystems communicate. Prover waits for a SequencerCommitment on DA before it can start proving BatchProof. But we don't need to do that!
What if Sequencer sends SequencerCommitments both on DA and directly to a Prover? Then Prover can start proving without waiting for DA to finalize.
In order to achieve that we have to split:
So the interaction of Sequencer-DA-Prover will be different:
But we have to deal with reorgs. If reorg happens:
UPD 1
What if we don't put SeqComs on DA? We may include them inside BatchProof so we don't need to create inclusion+completeness proof for SeqComms at all.
But we may even go further and remove SequencerCommitments from BatchProof, because BatchProof is the new source of trust for the new state no matter what.
Beta Was this translation helpful? Give feedback.
All reactions