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
After a genesis upgrade, CometBFT will only start an InitChain handshake if the application height is zero (i.e. pre-genesis). Currently, we do not systematically overwrite the height of the full node. While this technically work, this is not upgrade flow that was tested by the cometbft team. Moreover, this forces chain parameter upgrades to be done in ad-hoc way during migration, instead of simply overwriting values in a genesis file. Instead, we should make pd support running InitChain with an initialized storage layer, and an arbitrary height start.
The text was updated successfully, but these errors were encountered:
Closes#1809, and prepares #3004 since we will be able to match the supplied genesis state to decide whether we want to run chain initialization logic e.g. setting the genesis base rate, or fast-forward to committing the initial height block.
This PR turns `genesis::AppState` into an enum:
```rust
pub enum AppState {
Content(/* a full genesis configuration */),
Checkpoint(/* a free-form byte string e.g. an apphash, a commit hash */)
}
```
and percolate those changes across the codebase.
The only remaining item is tracking the active validator set and forwarding it to CometBFT across the upgrade boundary. Then checking that this correctly does not break a penumbra light client.
After a genesis upgrade, CometBFT will only start an
InitChain
handshake if the application height is zero (i.e. pre-genesis). Currently, we do not systematically overwrite the height of the full node. While this technically work, this is not upgrade flow that was tested by the cometbft team. Moreover, this forces chain parameter upgrades to be done in ad-hoc way during migration, instead of simply overwriting values in a genesis file. Instead, we should makepd
support runningInitChain
with an initialized storage layer, and an arbitrary height start.The text was updated successfully, but these errors were encountered: