Shargon

> This will change the behavior of existing contracts as well. Yes, we need a fork, but currently we allow integers out of the range

> > Yes, we need a fork, but currently we allow integers out of the range > > Its not about a fork, it is that you have changed the...

@Jim8y is right, a fork don't solve that the contract was not updated, maybe we need to store in the contract the last updated/deploy height, and use it as a...

> > @shargon @Jim8y Something is incompatible. Blockchain stopped syncing at block `1528989` on mainnet.   > > Please consider close this pr. @shargon But it can't be related...

> @shargon @superboyiii can we add this in `3.9.0`? First we need to > @shargon @superboyiii can we add this in `3.9.0`? If it's added I can move this PR...

I'm good with it, it will make cheaper the executions, it's good for all

For me is something that doesn't hurt anyone, it only improves, and we can add it without problems with the jumpTable now.

> As a result I think that in many cases [StdLib.jsonSerialize](https://github.com/neo-project/neo/blob/77ee2cc5b6ea371efdf3be506b173c6304b0fc01/src/Neo/SmartContract/Native/StdLib.cs#L44) can fail e.g. as soon as the provided stack item contains a script hash like this example script that...

@AnnaShaleva please move this PR to neo-node repository

Old, if remains, please re-open