Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

block signature rollup #18

Open
dabasov opened this issue Mar 10, 2020 · 0 comments
Open

block signature rollup #18

dabasov opened this issue Mar 10, 2020 · 0 comments

Comments

@dabasov
Copy link
Collaborator

dabasov commented Mar 10, 2020

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:

  1. Add signature aggregate to block
  2. Prune signatures
  3. 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
  4. 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.
  5. When synchronizing blockchain, we must do the same operation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant