Support syncing from LightSyncState
#12
Labels
I5-enhancement
An additional feature request.
Comments
|
cc #60 |
Yeah that should be tackled first |
the-right-joyce
added
I5-enhancement
fixxxedpoint
pushed a commit
to fixxxedpoint/polkadot-sdk
that referenced
this issue
Aug 5, 2024
…tworkWorker. Every such implementation should provide authentication and muxing mechanisms. (paritytech#9)" (paritytech#12) This reverts commit 8522cd0.
fixxxedpoint
added a commit
to fixxxedpoint/polkadot-sdk
that referenced
this issue
Aug 5, 2024
…etworkWorker. Every such implementation should provide authentication and muxing mechanisms. (paritytech#9)" (paritytech#12) This reverts commit 8b80e54.
liuchengxu
added a commit
to subcoin-project/polkadot-sdk
that referenced
this issue
Sep 20, 2024
* Add Dockerfile * Docker cache layer * Remove debug info from release profile * Remove build for docker branch * Add TODO
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have the
LightSyncState:https://github.com/paritytech/substrate/blob/2924b0183764b18ad4d79037c67652fb2f1aaa01/client/sync-state-rpc/src/lib.rs#L112-L125
This is for example used by smoldot to not sync from genesis to the tip of the chain. So, this decreases the time to sync to the tip of the chain. The other advantage is also that, if put after a forced set change, warp sync still works as it doesn't encounter the forced set change.
The
LightSyncStateis an optional extension of the chain spec as it requires that a chain is using Babe/Grandpa. So, currently only Polkadot/Kusama/Testnets are using this. An implementation should also not enforce that these values are being passed.The text was updated successfully, but these errors were encountered: