-
Notifications
You must be signed in to change notification settings - Fork 19
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
Enable Warp Sync #1585
Comments
How do we test warp sync to ensure integrity of data and consensus? |
The security is based on the relay chain peering. If we have a state with a root that matches one on the relay chain, then we know that state is good. For warping the relay chain, it is almost the same, except it is that the additional blocks are built on the warp'd block. While it is possible to chose a bad warp provider it is no different that choosing a bad chain spec or connecting to a bad bootnode. |
It's not clear that Warp sync will work with Aura consensus but there are examples of it working with Grandpa. More research is needed. |
Appears to be possible: paritytech/cumulus#1909 Yup added in |
# Goal The goal of this PR is to enable Warp sync for Frequency Closes #1585 # Discussion - There are some additional updates possible to `node/service/src/service.rs` that are possible once #1639 is complete - Mostly this swaps out for the standard setup from cumulus # Testing 1. `make build-mainnet-release` 2. `./target/release/frequency --tmp --sync warp -- --tmp --sync warp` 3. Look for `[Parachain] ⏩ Waiting for pending target block` 4. Wait until `[Parachain] ⏩ Block history` 5. Finally `[Parachain] ✨ Imported` (aka warp complete)
# Goal The goal of this PR is to enable Warp sync for Frequency Closes #1585 # Discussion - There are some additional updates possible to `node/service/src/service.rs` that are possible once #1639 is complete - Mostly this swaps out for the standard setup from cumulus # Testing 1. `make build-mainnet-release` 2. `./target/release/frequency --tmp --sync warp -- --tmp --sync warp` 3. Look for `[Parachain] ⏩ Waiting for pending target block` 4. Wait until `[Parachain] ⏩ Block history` 5. Finally `[Parachain] ✨ Imported` (aka warp complete)
Warp sync allows fast syncing and is currently not working. After #1270, we should be able to enable it.
Related:
Note that warp sync does not work on the Rococo Relay chain (although still works on the Frequency Testnet)
The text was updated successfully, but these errors were encountered: