ghost!@shell

This wrong ledger corresponds to this orphaned block: https://minaexplorer.com/block/3NKm5VGDQXtekWf3erWfjcHciGzjAWB4u7WNE7gAHGYjvkFbF5xj and in our mainnet db dump, the user_commands and internal_commands for those 2 blocks are the same.

So this is caused by a minor bug that's already been fixed. When running replayer around 146033 - 146752 slots, please use the `--continue-on-error` flag and with `--checkpoint-interval 1000` In...

The PR seems good to me. This can be tested using the mina_local_network script.

For the migrated database we should keep the blocks from previous chain (blocks with protocol_version = 2 in this emergency hard fork for example) to be still canonical. Is this...

Do we also need the `mina-create-legacy-ledger` to run this?

!ci-build-me

!ci-nightly-me

!ci-build-me

!ci-build-me

!ci-nightly-me