You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once state sync ships, we should add support for bootstrapping a node with state that has been obtained by other means as well (e.g. by copying the application state directory) - i.e. instead of fetching and restoring an ABCI snapshot, simply use some existing local state to bootstrap.
This could e.g. be done by adding a use_local_state option to the [statesync] section, which would cause state sync to skip straight to the verification and bootstrap step, possibly with light client verification if necessary.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
This is useful for custom state sync `StateProvider` implementations that need to build new states for bootstrapping the node. It will also be useful when implementing other mechanisms to bootstrap nodes, e.g. #4642 and #3713.
Once state sync ships, we should add support for bootstrapping a node with state that has been obtained by other means as well (e.g. by copying the application state directory) - i.e. instead of fetching and restoring an ABCI snapshot, simply use some existing local state to bootstrap.
This could e.g. be done by adding a
use_local_state
option to the[statesync]
section, which would cause state sync to skip straight to the verification and bootstrap step, possibly with light client verification if necessary.For Admin Use
The text was updated successfully, but these errors were encountered: