-
Notifications
You must be signed in to change notification settings - Fork 325
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
Metropolis Plan Discussion #4
Comments
you have double Parity there |
Thanks Roman! |
@Souptacular not "ethereumjs-lib" just "ethereumjs" |
@Souptacular as possible it would be great to have the EIPs ordered by likelyhood of them being included in the next feature fork |
That's a great idea. I currently do not have enough knowledge of the EIPs and their discussion history to make that call. It would be great if someone else could. @obscuren, @chriseth, @vbuterin, @gavofyork: If any of you have time to quickly put a comment with what you consider to be the most likely to be implemented EIPs I can reorder the chart. |
ethereum/EIPs#166 : why do we need another replay protection? |
go-ethereum |
@Nashatyrev Please ask in the the EIP Issue page for #166 and tag @vbuterin |
The chart has been updated to correct some inaccurate potential EIPs. |
@Souptacular does it make sense to add "yellowpaper" as a client in the chart? |
What about delaying the diff.bomb and eventually decrease inflation (EIP#186/#189)? The Eth-community should have a possibility to vote on this. |
Is their any plan to include a byte code / EVM versioning scheme like #154 in Metropolis? |
NOTE: OUTDATED. Please see: https://github.com/ethereum/EIPs/blob/master/README.md for latest accepted EIPS.
Metropolis Discussion
Use this issue for discussion around Metro. I will update chart/todo list as comments come in.
Approximate ice age start (according to Vitalik):
Metropolis Todo
EIP Implementation Chart
Note: The EIPs listed in the chart are not necessarily approved for Metro via the EIP acceptance process, but we want to get information as early as possible.
The text was updated successfully, but these errors were encountered: