Skip to content

AllCoreDevs Meeting 9 Agenda #3

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
Souptacular opened this issue Jan 11, 2017 · 6 comments
Closed

AllCoreDevs Meeting 9 Agenda #3

Souptacular opened this issue Jan 11, 2017 · 6 comments
Labels
ACD Type: All Core Dev calls - execution & consensus Execution Layer: Issues that affect the execution layer

Comments

@Souptacular
Copy link
Contributor

Souptacular commented Jan 11, 2017

All Core Devs Meeting 9 Agenda

Meeting Date/Time: Wednesday 1/25/17 at 14:00 UTC.

Meeting Duration 1.5 hours

Agenda

Please provide comments to add or correct agenda topics.

  1. Should we set up a set meeting time? The first and third Friday of every month at 14:00 UTC maybe? Given enough notice, we can push these meetings back or forward a week due to major events that multiple core devs will be attending (such as Edcon Feb. 14th).
  2. Come to final agreement on EIP5/8 [Facilitator: Christian]
  3. Precompiles for elliptic curve point addition, elliptic curve scalar multiplication and pairing [Facilitator: Christian]
  4. Metropolis and associated EIPs. [Facilitator: Vitalik]
  1. New general state tests: General State Tests Proposal EIPs#176 . [Facilitator: Martin S.]
  2. STATIC_CALL: New opcode: STATIC_CALL EIPs#116 with additional points to discuss. [Facilitator: Christian]
    Do we want three call variants:
    (1) anything is possible (current call)
    (2) state modifications are disallowed
    (3) state modifications and state reads are disallowed (except for code) furthermore, do we want a special call opcode that fails if the target does not contain code?
  3. EIP 141: EVM opcode: designated invalid instruction. [Facilitator: Christian]
  4. Difficulty bomb block 3.5 mil. is < 3 months away. Reference to previous calculations. [Facilitator: Martin S.]
  5. New EIP GitHub process and cleanup. See details here [Facilitator: Hudson]
@chriseth
Copy link
Contributor

  • Come to final agreement on EIP5/8
  • Precompiles for elliptic curve point addition, elliptic curve scalar multiplication and pairing

@holiman
Copy link

holiman commented Jan 11, 2017

@chriseth
Copy link
Contributor

chriseth commented Jan 17, 2017

STATIC_CALL: ethereum/EIPs#116 with additional points to discuss:

  • do we want three call variants: (1) anything is possible (current call) (2) state modifications are disallowed (3) state modifications and state reads are disallowed (except for code)
  • furthermore, do we want a special call opcode that fails if the target does not contain code?

@holiman
Copy link

holiman commented Jan 20, 2017

How about https://www.reddit.com/r/ethereum/comments/4iozgf/in_around_14_month_the_difficulty_bomb_will_make/d30c0lq/ . It's less than three months left to block 3.5M . If I interpret it correctly, we should plan a HF somewhere within the coming couple of months.

@chriseth
Copy link
Contributor

Oh and this one should be quick: ethereum/EIPs#141 - designated invalid opcode

@Souptacular
Copy link
Contributor Author

Souptacular pushed a commit that referenced this issue Apr 12, 2017
timbeiko added a commit that referenced this issue Jun 25, 2020
timbeiko added a commit that referenced this issue Jun 25, 2020
Add implementers call #3 info
timbeiko pushed a commit that referenced this issue Apr 8, 2021
timbeiko pushed a commit that referenced this issue Nov 11, 2021
@nixorokish nixorokish added ACD Type: All Core Dev calls - execution & consensus Execution Layer: Issues that affect the execution layer labels Feb 4, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
ACD Type: All Core Dev calls - execution & consensus Execution Layer: Issues that affect the execution layer
Projects
None yet
Development

No branches or pull requests

5 participants