Rootul P

lol what is returning app version 2?! The v1 state machine returned nil consensus params ``` EndBlock height 1 invoked with current app version 1 EndBlocker invoked on state machine...

It looks like the v1 application thinks it is a v2 application: ``` panic: current app version 1 does not match app version from current app 2 ``` InitChain is...

``` EndBlock height 3 invoked with current app version 1 EndBlocker invoked on state machine v1 with req.Height 3 v1 application should upgrade to v2 at hard-coded upgrade height 3...

Current issue is that even though the v2 state machine runs migrations and initializes KV stores, it doesn't have params initialized. So next steps are to look into where exactly...

Added a bit more logs and learned that the param in question is only set during the `x/blob` module's `InitGenesis`. `InitGenesis` is only ever invoked on the v1 state machine:...

``` Multiplexer EndBlock height 9 with current app version 2 next app version 2 returned app version 3 Multiplexer Commit invoked with current app version 2 E[2024-08-13|15:27:45.011] CONSENSUS FAILURE!!! module=consensus...

My impression is that when a user upgrades from existing v1.x.x to v2.0.0, they stop their v1.x.x node, download the v2.0.0 binary and start it. When it starts, it gets...

Notes from call w/ Evan + Callum - Check if a bank balance exists in v2 state machine / v3 state machine to identify if just params are missing in...

The application and CometBFT both use the same DB (by default a goleveldb inside `~/.celestia-app/data`). However the default can be overriden via CLI flags or config file.

I think the current error is occurring because this isn't happening on the prototype: ``` 3:42PM INF Completed ABCI Handshake - CometBFT and App are synced appHash="���B��\x1c\x14���șo�$'�A�d��L���\x1bxR�U" appHeight=0 appVersion=1 module=consensus...