-
Notifications
You must be signed in to change notification settings - Fork 823
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
Make Warp Sync the default Sync mode #34
Comments
I am a bit concerned about this because it implies a bunch of assumptions about properties of the chain like consensus and with Substrate being a generic framework it would be unfortunate to have our chain broken because the default sync is no longer compatible with it. I'm not sure what is the scope of this issue though, maybe we can patch it and override the default mechanism somehow even after this change 🤷 |
Good point and clearly something that should be considered while doing this :) |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/community-bootnodes-and-snapshot-providers/630/1 |
…tech#34) Signed-off-by: Robert G. Jakabosky <rjakabosky+neopallium@neoawareness.com>
…eiris/actions-gh-pages-3.9.3 Bump peaceiris/actions-gh-pages from 3.8.0 to 3.9.3
* reward submitters on finalization * fix grumble * make submitter part of ImportContext
* Remove dummy build_system_rpc_future() * Add protocol id to chain spec * Fix clippy
We should make warp sync the default sync mode. Only if someone starts with
--state-pruning archive
we should switch to the catch up sync mode, aka download and execute every block.This depends on: #35
The text was updated successfully, but these errors were encountered: