Forks are fail when objects get changes (number OR name of the properties of an object)

[golnar-m]

Hello,

We have an issue. We've stored some objects in the kvstore and in our testnet some clients started to use our blockchain.

Now we changed 2 of the objects, for one of them we increased the number of the properties and the second object we changed the name of a property.

Now, after fork we have a problem with already registered clients, we can not GetClientObject after these changes. Because they are forked from the previous client object.

We created fork with below steps:

1- Pull the new code
2- Build the binary
3- The new binary will be replaced with the old one
4- And when we do soarchaind start again the new binary will run with the already saved data which is a "hard fork" basically.

Is there a solution for this?

[golnar-m]

Answered,

[julienrbrt]

For future reference: #17103 (comment)