Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Cross-msgs should be batched if checkpoint signing window passes? #156

Open
adlrocha opened this issue Mar 25, 2022 · 0 comments
Open

Cross-msgs should be batched if checkpoint signing window passes? #156

adlrocha opened this issue Mar 25, 2022 · 0 comments

Comments

@adlrocha
Copy link
Collaborator

adlrocha commented Mar 25, 2022

In the current implementation, the SCA batches in the checkpoint template all the cross-msgs that need to be propagated in the checkpoint. After the checkpointing window passes, the signing window opens for an additional period in which miners can populate the template, sign it, and submit it to the parent. When the signing window passes, the checkpoint template is overwritten with the next one, which means that if the checkpoint is not successfully signed the cross-messages for that checkpoint are lost.

We should buffer the checkpoint template and check in the parent if the checkpoint has been successfully propagated so we don't lose cross-message for propagation (this may be partially fixed in #144)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant