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
To implement rollups we need a way to store block's validity fact. To prove the validity of the block we use signature aggregated during voting phase is is exactly what we are going to use as block's validity fact. We can go further and prune all transaction signatures as they become obsolete when majority of nodes voted for this block and validated it.
To implement this change we need:
Add signature aggregate to block
Prune signatures
Update block's signature every time we add new block, since added block can contain QC, we can simply put this signature to local QC.block and prune it's transactions
When validating block, first we check it's signature aggregate and if absent validate transaction signatures as usual, if signature is correct we prune transaction's signatures.
When synchronizing blockchain, we must do the same operation
The text was updated successfully, but these errors were encountered:
To implement rollups we need a way to store block's validity fact. To prove the validity of the block we use signature aggregated during voting phase is is exactly what we are going to use as block's validity fact. We can go further and prune all transaction signatures as they become obsolete when majority of nodes voted for this block and validated it.
To implement this change we need:
The text was updated successfully, but these errors were encountered: