EIP-1707: Use Version Byte Prefix for Contract Account Versioning

[sorpaas]

(See https://specs.that.world/26-ver/ for the newest version of the spec.)

Provide an alternative proposal compared with EIP-1702 / ECIP-1040, with the following advantages:

• We don't need to modify existing account state format.
• We don't need to modify how precompiled contracts are invoked.
• Compatible with the standard WebAssembly binary format.

[axic]

Please also check #154. I have another pending EIP for defining the actual version numbers.

[axic]

Can you please rebase to bring in new CI checks?

Please also add the missing sections (Abstract, Motivation, Rationale, Test Cases, Implementaiton).

[axic]

@sorpaas you can also mark this "Abandoned", but since there were so many discussions about versioning I'd suggest we do merge this.

[sorpaas]

@axic Done! I also added a superseded-by tag to 1702, to indicate that this proposal is dropped in favor of 1702 which serves the same functionality. Not sure if we have a better tag.

[sorpaas]

@axic CI returns this error:

EIPS/eip-1707.md is NOT valid:	 {:status=>["is not included in the list"]}

Apparently Abandoned status has not yet been added to the automerger bot.

[axic]

Yes, it is being fixed :(

[axic]

Will be fixed by #2161.

@sorpaas Can you add an "Abstract"? And the other missing sections, where you can just ad TBD.

[axic]

@sorpaas Abandoned is now accepted if you forward to master, but please address the above comments too.

[sorpaas]

@axic Sorry for the delay. I'll get this done soon.

[sorpaas]

I have decided to withdraw this for EIP publication due to licensing requirements. The newest version of this spec can be seen here: https://specs.that.world/26-ver/