Pavel Zbitskiy

let's not merge anything. Instead, either cherry-pick [c1c0146](https://github.com/algorand/go-algorand/pull/4424/commits/c1c01467e5d1884bb8ed590300a7c14db732b13f) or use this commit as an example

overrun by #4428

I suggest to postpone it until after the release

What we want to accomplish with this? To allow developers to debug their contracts at round? Or something else?

As note in the [comment](https://github.com/algorand/go-algorand/pull/4003#discussion_r898450194) we might use this https://github.com/algorand/go-algorand/blob/master/util/db/initialize.go#L34 to rewrite migrations and simplify the code.

`calculateCatchpointRounds` has a problem in case of unordered commits and commit ranges greater than the catchpoint interval - in this case min might be greater than max, and the second...

Looks like the problem came from inconsistent usage of `calculateCatchpointRounds` in producer and consumer.

@cce up

Thank you for the report. What is in `node.log` ?

Catchpoint apply code appears broken feature > ~/go/bin-cp-oom/catchpointdump net -l -n betanet.algodev.network -r 19780000 -s [ Done ] Downloaded http://r4.betanet.algodev.network:4160/v1/betanet-v1.0/ledger/brycg [ Done ] Loaded Unable to load catchpoint file into...