-
Notifications
You must be signed in to change notification settings - Fork 242
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
Fast Sync Support for Domains #1582
Comments
Hi @jfrank-summit @vedhavyas what is the status on this? Since I recently worked on upstream sync issues, can start looking at this if this is still important. |
This is not required for mainnet beta and I am not sure if the work you did upstream would be helpful here. @vedhavyas thoughts? |
We would definitely require this for domain nodes to sync from other domain nodes rather than deriving the domain blocks from the consensus blocks. We do not have any specific discussion on how to approach this since this involves network for domains and maybe other things I might have missed. This is not a highest priority since we do not plan to have this for mainnet beta. |
Closing in favor of #2616 as duplicate |
Support fast sync of the state from a state root commitment (checkpoint) stored on the system domain registry. This will likely modify or extend the warp sync mechanism already included with Substrate. Once implemented this will be the default sync mechanism for new operators who join the domain subnet. This assumes there is at least one honest and live operator available, if not use the fallback naive sync.
The text was updated successfully, but these errors were encountered: