AllCoreDevs Meeting 9 Agenda
Souptacular opened this issue · 6 comments
Souptacular commented
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.
- 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).
- Come to final agreement on EIP5/8 [Facilitator: Christian]
- Precompiles for elliptic curve point addition, elliptic curve scalar multiplication and pairing [Facilitator: Christian]
- Metropolis and associated EIPs. [Facilitator: Vitalik]
- ethereum/EIPs#101 (bigint arithmetic)
- ethereum/EIPs#140 ("cheap throw" by Nikolai)
- ethereum/EIPs#100 (uncle mining incentive fix)
- ethereum/EIPs#96 (putting block hashes and state roots into the state)
- ethereum/EIPs#86 (abstraction)
- New general state tests: ethereum/EIPs#176 . [Facilitator: Martin S.]
- STATIC_CALL: ethereum/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? - EIP 141: EVM opcode: designated invalid instruction. [Facilitator: Christian]
- Difficulty bomb block 3.5 mil. is < 3 months away. Reference to previous calculations. [Facilitator: Martin S.]
- New EIP GitHub process and cleanup. See details here [Facilitator: Hudson]
chriseth commented
- Come to final agreement on EIP5/8
- Precompiles for elliptic curve point addition, elliptic curve scalar multiplication and pairing
holiman commented
- New general state tests: ethereum/EIPs#176 . cc @winsvega
chriseth commented
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 commented
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 commented
Oh and this one should be quick: ethereum/EIPs#141 - designated invalid opcode
Souptacular commented
Notes and audio posted to https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%209.md
Closing issue.