Stop breaking database compatibility!

[532910]

Why the hell does this happens almost on every release? The only possible place for such things is major releases, like for APIs, protocols, etc.

[AnnaShaleva]

We don’t have major releases now, thus, every time the DB format is being changed we update the minor version. This scheme won’t be changed until we have major version.

Why the hell does this happens almost on every release?

We do change the DB format only in emergency cases or for incompatible features.

[532910]

0.103.1 is not even a minor version, it's a PATCH!

[roman-khimov]

And it's state-compatible with 0.103.0. 100%. It's just that some (and frankly, maybe just a single one on a single network, #3190) application logs can be bad.

[roman-khimov]

We will do resynchronizations until we have state roots in the header, see neo-project/neo#1526, that's just inevitable. And to be fair, it's not that bad with NeoGo, try synchronizing a C# node and you'll realize that you're lucky to be able to do that in a few hours.