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.

Sign up for GitHub

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

Jump to bottom

All Core Devs Meeting 17 Agenda #15

Closed
Souptacular opened this issue May 27, 2017 · 3 comments
Closed

All Core Devs Meeting 17 Agenda #15

Souptacular opened this issue May 27, 2017 · 3 comments

Comments

@Souptacular
Copy link
Contributor

Souptacular commented May 27, 2017 •
edited
Loading

All Core Devs Meeting 17 Agenda

Meeting Date/Time: Friday 6/3/17 at 14:00 UTC

Meeting Duration 1.5 hours

YouTube Live Stream Link

Agenda

  1. Update on the proposal: "Freeze" EIPs to allow for testing. [Yoichi/Hudson]
  2. Metropolis updates/EIPs.
    a. Details and implementations of EIPs.
    - Need items [submit in comments below].
    b. Updates to testing.
    - more static call tests added
    - blockhash changes (eip96) about to be merge in cpp develop
    - documentation in progress
    c. Any "subtleties" we need to work out.
    - Need items [submit in comments below].
    d. Review time estimate for testing/release.
    - Need items [submit in comments below].
  3. TRXID opcode: TRXID opcode EIPs#222 [Jan]

Please provide comments to add or correct agenda topics.
@janx
Copy link
Member

janx commented May 31, 2017

TRXID opcode: ethereum/EIPs#222

@5chdn
Copy link
Contributor

5chdn commented Jun 21, 2017 •
edited
Loading

Edit: I was suspecting this to be the next meeting but it's a past meeting. Please add this below to the next meeting which does not seem to have any ticket yet.

The missing EIP for the difficulty bomb should be discussed / specified. ethereum/EIPs#649

I couldn't find any details except that comment by Peter suggesting "that we add special rules to the difficulty calculation to effectively pause the difficulty between different blocks".

If we could get this into this meeting, we can specify and implement it afterwards.

@Souptacular
Copy link
Contributor Author

Need notes for this meeting. Closing agenda issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@janx @Souptacular @timbeiko @5chdn