Skip to content
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

Istanbul Hardfork Meta Issue #501

Closed
17 of 18 tasks
holgerd77 opened this issue Apr 29, 2019 · 7 comments
Closed
17 of 18 tasks

Istanbul Hardfork Meta Issue #501

holgerd77 opened this issue Apr 29, 2019 · 7 comments

Comments

@holgerd77
Copy link
Member

holgerd77 commented Apr 29, 2019

Entry points for information:

EIP Working List:

Other TODOs:

We should as time/decisions progresses create separate issues for accepted EIPs and discuss implementation details there.

@axic
Copy link
Member

axic commented Apr 29, 2019

On the last ACD call it was decided that https://eips.ethereum.org/EIPS/eip-1679 is the canonical source of information for proposed EIPs. It should be enough to follow that.

@holgerd77 holgerd77 mentioned this issue Apr 29, 2019
23 tasks
@holgerd77
Copy link
Member Author

@axic Ah ok, thanks!

@holgerd77
Copy link
Member Author

Grabbed this Istanbul EIP Readiness Checklist from the EIP Gitter channel, super-detailed and helpful.

Still not 100% sure on the process though and what EIPs will finally be included. As far as I got comments from @bmann on ACD Gitter, there seems to be the need for a reference implementation of an EIP to be included, not sure if there also needs to be a final ok from ACD call and if there is/will be some general limitation in scope at some point to not overload.

I would suggest we start with some low-level stuff from the spreadsheet, this opcode renaming EIP-1803 has made it pretty far and will likely be included, since it wouldn't make sense to postpone such a trivial change.

Will open an issue on that so that we get the process going.

@holgerd77
Copy link
Member Author

holgerd77 commented May 25, 2019

Truffle/Ganache: @davidmurdoch @benjamincburns
Remix: @yann300 @LianaHus
Others: Please drop a note if you are using the VM in your library in a HF relevant context

We are now starting Istanbul integration, just to let you know. I would suggest you follow the process a bit and start early on with a draft integration so that users can early on start to experiment with new features. This will take an important role in helping to prevent such a chaotic last-minute situation as happened during along the last Constantinople/Petersburg hardfork 😛.

We are also very close on merging the TypeScript transition work from @s1na here #479 into master and will publish a beta v4 release on this during next week. This is also coming with heavy internal changes, the outer API stays unchanged though for now. The inner structure is not completely finalized and will likely further change to some extend on the way towards a final release. You are very much invited to have a look, do your thoughts on that and hook into the process.

If you have any questions on Istanbul respectively v4 let us know! 😄

Cheers
The EthereumJS Team

@holgerd77 holgerd77 changed the title Istanbul Planning Istanbul Hardfork Planning Jul 31, 2019
@holgerd77 holgerd77 changed the title Istanbul Hardfork Planning Istanbul Hardfork Meta Issue Jul 31, 2019
@holgerd77
Copy link
Member Author

Have updated the initial post with a new EIP working list, please check once finished.

@holgerd77
Copy link
Member Author

TODO: add EIP-2200 and EIP-1884 accepted in ACD #68 to the list, create separate task issue on the appropriate libraries.

@holgerd77
Copy link
Member Author

Solved by #596 and following PRs, will close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants