-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling Retroactive Changes (e.g. EIP-2681) #12
Comments
@lightclient is this still relevant? Would this proposal help with it? ethereum/pm#295 |
I suppose we can close this. I think this plays into the long term vision of moving to and eth2-like spec definition for ethereum. In that case, this question is trivial: just update the spec. Today, it is less trivial because "Final" on an EIP doesn't mean included on mainnet. But retroactive changes are confusing because they aren't included in a fork, so it's unclear how to signal that they are "canonical". |
Here's one solution: #401 And here's another: ethereum/yellowpaper#813 |
Just Do It ™️ |
There was no dissent in moving EIP-2681 forward during ACD 101. The problem is, what does that mean? With the separation of EIPs and network upgrades, "Final" doesn't mean mainnet.
Typically this isn't a major issue, because we can use the upgrade tracker and once its scheduled in an upgrade it is recorded during that transition. But EIP-2681 sets a limit on account nonces retroactively from genesis. My guess is that a modification should be made to the Yellow Paper as it is the most canonical spec for Ethereum?
cc: @axic, @MadeofTin, @Souptacular
The text was updated successfully, but these errors were encountered: