Create Meeting 58.md #91
Conversation
All Core Devs Meetings/Meeting 58.md
Outdated
|
|
||
| ### DECISIONS MADE | ||
|
|
||
| **DECISION 58.1** The [ProgPoW Carbon Vote](http://www.progpowcarbonvote.com/) signal will be shutting down in 13 days from today. Everyone that wishes to vote will need to do so before this date and ensure they leave their ETH in the address they voted from until after the specified block number. |
There was a problem hiding this comment.
This wasn't in the call, but Lane has since then defined the block number. May be worth including: https://twitter.com/lrettig/status/1111652965331415040
There was a problem hiding this comment.
Good call - updated.
All Core Devs Meetings/Meeting 58.md
Outdated
|
|
||
| **ACTION 58.2** Review the proposed solutions for Roadmaps in the [Ethereum Magicians](https://ethereum-magicians.org/t/more-frequent-smaller-hardforks-vs-less-frequent-larger-ones/2929) forum to decide if going forward the Core Devs adopts smaller hardforks rather than larger hardforks. | ||
|
|
||
| **ACTION 58.3** Vitalik to format the currently proposed EIP-1559 so that it is correctly presented. |
There was a problem hiding this comment.
Perhaps link it? ethereum/EIPs#1559
|
|
||
| **ACTION 58.4** Lane to provide a block number for when the [ProgPoW Carbon Vote](http://www.progpowcarbonvote.com/) will be shutdown. | ||
|
|
||
| **ACTION 58.5** Discuss if ProgPoW should continue to be implemented if the Technical Audit is not funded in [Ethereum Magicians](https://ethereum-magicians.org/tags/progpow) or [here](https://ethereum-magicians.org/t/what-has-to-be-done-to-get-progpow-on-ethereum/1361) or [here](https://ethereum-magicians.org/t/motion-to-not-include-progpow-without-audit/3027). |
There was a problem hiding this comment.
A lot of conversation has happened here, may be worth linking too: https://ethereum-magicians.org/t/motion-to-not-include-progpow-without-audit/3027
There was a problem hiding this comment.
Already in the list of links.
|
|
||
| **ACTION 58.6** Clients should provide updates for future Core Dev Calls in the comments of the agenda and request an update to the agenda if they wish to discuss anything specific. | ||
|
|
||
| **ACTION 58.7** Research should provide updates for future Core Dev Calls in the comments of the agenda and request an update to the agenda if they wish to discuss anything specific. |
There was a problem hiding this comment.
Nit: This and the one above are duplicated in the "Decisions" section above.
There was a problem hiding this comment.
Agree, there is an element of duplication but one was a decision regarding no longer having generic updates in the meeting and the other is to direct the Clients and Researchers to start providing updates in the comments of the agenda.
|
Thank you @timbeiko for the review and updates. |
Please review and if appropriate add to the PM Notes.