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
The current way to synchronize a story node from block 0 to the latest height can be a very complicated process, especially when the network has gone through multiple hard fork upgrades. In this case, the node runner must download multiple binaries, each binary for each hard fork version, and manually switch the binaries at each hard fork block height.
Many node runners in the cosmos ecosystem use cosmovisor to automate the binary switching process. But even cosmovisor doesn't support upgrades on multiple binaries.
We should support a single binary that is backward-compatible with all the hard fork versions to make the node runners' lives easier, which is similar to Ethereum's implementation.
Suggested solution
Investigate Celestia's CIP-10 and it's signal module.
Definition of done
Have a working and fully tested single binary solution
The text was updated successfully, but these errors were encountered:
Description and context
The current way to synchronize a story node from block 0 to the latest height can be a very complicated process, especially when the network has gone through multiple hard fork upgrades. In this case, the node runner must download multiple binaries, each binary for each hard fork version, and manually switch the binaries at each hard fork block height.
Many node runners in the cosmos ecosystem use cosmovisor to automate the binary switching process. But even cosmovisor doesn't support upgrades on multiple binaries.
We should support a single binary that is backward-compatible with all the hard fork versions to make the node runners' lives easier, which is similar to Ethereum's implementation.
Suggested solution
Investigate Celestia's CIP-10 and it's signal module.
Definition of done
Have a working and fully tested single binary solution
The text was updated successfully, but these errors were encountered: