Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

BEEFY sync protocol #20

Closed
2 tasks
tomusdrw opened this issue Nov 2, 2020 · 4 comments
Closed
2 tasks

BEEFY sync protocol #20

tomusdrw opened this issue Nov 2, 2020 · 4 comments
Assignees
@acatangiu
Labels
ideas Something to keep in mind, but not necessarily instantly actionable. M-gadget The client code of the gadget. R-substrate The issue has to be implemented in the Substrate repo
Milestone
BEEFY on Kusama

Comments

@tomusdrw
Copy link
Contributor

tomusdrw commented Nov 2, 2020

Currently the node has to be on-line to receive and store BEEFY justifications. If it falls behind it can rely on syncing the justification data along with the blocks (see #17), but there is no guarantee that we will get all of them (depends on who do we sync from).

Syncing only BEEFY justifications is also useful for Super Light Clients (see paritytech/parity-bridges-common#323 - beyond Solidity) - we could for instance sync Substrate Connect with this (see also paritytech/substrate#1208).

We should probably introduce:

  • BEEFY justification gossip
  • Sync protocol only for essential BEEFY justifications (session change blocks, era change blocks).
@tomusdrw tomusdrw added enhancement New feature or request M-gadget The client code of the gadget. ideas Something to keep in mind, but not necessarily instantly actionable. and removed enhancement New feature or request labels Nov 2, 2020
@seunlanlege
Copy link

seunlanlege commented Nov 13, 2021 •
edited
Loading

Would love to use this to get to understand substrate's networking protocol better. Is there mentorship available for this task?

@tomusdrw tomusdrw added this to the BEEFY on Kusama milestone Nov 26, 2021
@tomusdrw
Copy link
Contributor Author

Details will be outlined in #320 soonish.
Related #183

@acatangiu acatangiu added this to BEEFY Jun 28, 2022
@acatangiu
Copy link
Collaborator

We want to add dedicated substrate protocol for this instead of using block-import or sync. Will come back with more details when we settle on a design.

@acatangiu acatangiu mentioned this issue Jun 28, 2022
Closed
@acatangiu acatangiu moved this to Backlog 🗒 in BEEFY Jun 28, 2022
@acatangiu acatangiu moved this from Backlog 🗒 to Need for Kusama 🗒 in BEEFY Jul 6, 2022
@seunlanlege seunlanlege moved this to In Progress in Bridging team board Jul 7, 2022
@acatangiu acatangiu added the R-substrate The issue has to be implemented in the Substrate repo label Jul 14, 2022
@acatangiu acatangiu self-assigned this Jul 14, 2022
@acatangiu acatangiu moved this from Need for Kusama 🗒 to In Progress 🛠 in BEEFY Aug 4, 2022
@acatangiu acatangiu mentioned this issue Aug 23, 2022
Closed
@acatangiu
Copy link
Collaborator

Closing here, tracking issue in paritytech/substrate#12093

Repository owner moved this from In Progress 🛠 to Done ✅ in BEEFY Aug 23, 2022
Repository owner moved this from In Progress to Done in Bridging team board Aug 23, 2022
@acatangiu acatangiu moved this to Draft in Parity Roadmap Sep 12, 2022
@acatangiu acatangiu moved this from Draft to Closed in Parity Roadmap Sep 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@acatangiu acatangiu

Labels
ideas Something to keep in mind, but not necessarily instantly actionable. M-gadget The client code of the gadget. R-substrate The issue has to be implemented in the Substrate repo
Projects
No open projects
BEEFY
Status: Done ✅
Milestone
BEEFY on Kusama
Development

No branches or pull requests
3 participants
@tomusdrw @seunlanlege @acatangiu