Skip to content

chain upgrades #45

@redshiftzero

Description

@redshiftzero

For the upcoming testnet, we don't need to have the upgrade story worked out. However, for a production deployment, we should come up with a plan for upgrades and test it out in a testnet. It could be something lightweight like:

  • Validators agree (off chain) on a target upgrade block height and time
  • Everyone builds and tests the new binary with whatever config changes are needed
  • At the target height, everyone stops their nodes, upgrades binaries and restarts the chain

This does not reset the chain height. But we could alternatively stop the network at the target height, export all the chain data, and effectively create a new chain with a new chain ID at height 0. I think the former is probably easier but open for discussion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions