neo
neo copied to clipboard
neo-project
Versioned Abi
Related to https://github.com/neo-project/neo/pull/2628#issuecomment-970313832
It is a little difficult. For private networks, it is difficult for them to start the genesis block with the latest version. Maybe it would be easier for us to resynchronize the blocks?
I think that we will need it, private networks can change the protocol.json and set the block 1 for version 1, I think that sync the chain in every change is not a solution. Also we can create an argument --private in order to deploy the last version.
Otherwise why NativeUpdateHistory is an array? this end's the native contract updates, if sometimes you prefer to resync the chain, only we need to set AvailableFromVersion to 0, and it's done.
This is a possibility as well, @shargon. This might help historically processing old functions in a correct manner.
We need to update the abi with a transaction. I think we need another solution.
Agree. If we set a height in settings every time when we upgrade, it's too heavy. I checked every tx result and balance after mainnet synced with the latest develop branch, they're the same with v3.1.0, so we'd better to release v3.2.0 first and give more time to solve this. For testnet, we plan to open a new one but still maintain the current (https://github.com/neo-project/neo-node/pull/852).
We need to update the abi with a transaction. I think we need another solution.
Then we can have failures before this transaction.
We need to update the abi with a transaction. I think we need another solution.
Please check this version