-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Conversation
andresilva
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works as well but we should rename AuthoritySetChangeProof then since it is no longer required that the given header is actually changing the authority set. This means that a warp sync proof can also include justifications for arbitrary blocks of a given set_id and still be valid, whereas previously we'd guarantee that the warp sync proof is minimal, i.e. it only includes finality proofs for the transitions and one extra for the latest block at the end.
|
We can still guarantee that the sync proof is minimal. Only the last proof fragment, when |
|
Asked Erin to deploy this on westend-connect nodes. Warp sync in smoldot is working. |
|
bot merge |
|
Trying merge. |
* Another tweak to GrandPa warp sync * Rename to WarpSyncFragment * Ensure proof is minimal
Another pull request on top of #8392
Changes:
verifythat the verification targets the header that comes with it, otherwise someone could send a different header where the authorities set change isn't the same.WarpSyncFinished. I don't understand why we needed to special-case the latest justification. It is now part of the proof, which is IMO more simple.