Jimmy

> > we should not fix it > > What do you mean not fix it? The bug? We should not fix a bug that is already there in the...

Again, you dont fix it in a way that change the existing contract behavior. And you dont ensure someone has reached the maximum or not cause you dont know all...

> You playing with people's potential money they have invested. This could be bad if a contract is doing `StdLib.JsonSerialize` and `StdLib.JsonDeserialize` for objects that deal with real funds or...

@superboyiii, please check the state compatibility.

@shargon format not a thing i can update, please check it.

> @shargon @Jim8y Something is incompatible. Blockchain stopped syncing at block `1528989` on mainnet.   Please consider close this pr. @shargon

@shargon conflicts, lets add hardfork if possible and make it merged into the hardfork pr. Such that no more conflict to maintain.

> e If we decide this, maybe we can also have some V2 opcodes, for instance, POPITEM, APPEND, to avoid DUP, but directly peek the item and update the stackitem...

v3.9 is already not priority, next big version is v3.8. can be removed when we really have to decide v3.9, otherwise this issue will be lost forever, and no one...

no plan for 3.9 yet, wont hurt anyone to mark it so that we can pick it up later.