Add: add previous block state to the block header

[Jim8y]

This pr focus on solving the problem of neo block state finality.

it will work along with neo-project/neo-modules#835

[cschuchardt88]

Older version nodes will get disconnected. This will cause network protocol problems. And nothing will be able to talk to each other or sync on new update without using new version.

Please fix!!!

PS:
Also please cancel the github action, its been running for 25 mins now. And there is no timeout, its eating resources.

[Jim8y]

not a problem for neo, cause without this, we will hace more serious problem.

[cschuchardt88]

Does this get sent over the network? in other words does it serialize and deserialize this new object?

[shargon]

I think that we need first #2942 and maybe this #3037 (comment)

[Jim8y]

I think that we need first #2942 and maybe this #3037 (comment)

We can add this later, but i wish we can have it before we release the next version, such that we can solve the state issue caused by further node update.

[vncoelho]

I think that we need first #2942 and maybe this #3037 (comment)

I think that everything can be packed together into next release

[Jim8y]

I think that we need first #2942 and maybe this #3037 (comment)

I think that everything can be packed together into next release

That is what i hope, cause otherwise we might just keep asking nodes to resync, and be careful of the node state difference.

[roman-khimov]

It's obviously incompatible and it needs a lot of care before we can consider merging. We also need to integrate notary before doing stateroots. That's why 3.7/3.8 plans were laid out the way they are. Trying to fix everything in a single huge release can break the thing too easily.

[cschuchardt88]

Like @roman-khimov said incompatible, Will prevent older version nodes that haven't upgraded to new version to get disconnected on sync or resync. I think we will need a fork? Or update Version number to 1 for block and blockheader.

[roman-khimov]

Version=1 will definitely be needed.