EIP-1707: Use Version Byte Prefix for Contract Account Versioning#1707
EIP-1707: Use Version Byte Prefix for Contract Account Versioning#1707sorpaas wants to merge 7 commits intoethereum:masterfrom
Conversation
|
Please also check #154. I have another pending EIP for defining the actual version numbers. |
axic
left a comment
There was a problem hiding this comment.
Can you please rebase to bring in new CI checks?
Please also add the missing sections (Abstract, Motivation, Rationale, Test Cases, Implementaiton).
|
@sorpaas you can also mark this "Abandoned", but since there were so many discussions about versioning I'd suggest we do merge this. |
|
@axic Done! I also added a |
|
@axic CI returns this error: Apparently |
|
Yes, it is being fixed :( |
|
@sorpaas |
|
@axic Sorry for the delay. I'll get this done soon. |
|
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/ |
(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: