EIP-1891: Contract-based Account Versioning #1891
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sorpaas
changed the title
axic
suggested changes
May 23, 2019
|
@axic Moved this to abandoned as well, and added superseded-by tag to 1702. |
|
Moved to 46-VER. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moved to 46-VER.
Provide an alternative proposal compared with EIP-1702 / ECIP-1040 /
EIP-1707, with the following advantages:
The basic idea is that we use a contract address' storage to store an
account's version bytes. Note that it is also possible to extend this
scheme to store other information about an account.