Ethereum Core Devs Meeting 29 Agenda

[Souptacular]

Ethereum Core Devs Meeting 29 Agenda

Meeting Date/Time: Friday 12/01/17 at 14:00 UTC

Meeting Duration 1.5 hours

YouTube Live Stream Link

Agenda

1. Testing Updates
   a. Fuzzer updates.
   b. New transaction tests folder structure.
2. Shall we require CC0 notices in EIPs?
3. New Project: JSON RPC Proxy / eth-agent
   a. Discussion: Project idea: HTTP Proxy for JSON-RPC aleth#4563
   b. Proof of Concept: https://github.com/chfast/json-rpc-proxy/releases/tag/v0.1.0a1
4. Does it remain the case that the Yellow Paper is intended to be Ethereum's formal specification?
5. POA Testnet unification [Update]
6. Core team updates.

Please provide comments to add or correct agenda topics.

[benjaminion]

Hi @Souptacular - is this a reasonable place to discuss the below and potentially add it to the agenda for this or a future call? The immediate connection is between your agenda point 2 and my 1.c.

---

The Yellow Paper GitHub declares that the YP is "Ethereum's formal specification". This is widely understood to be the case. The YP is an immensely useful, authoritative, single point of reference for many aspects of Ethereum client implementations.

Question: does it remain the case that the YP is intended to be Ethereum's formal specification?

1. If yes, then it should be noted that the YP is currently significantly out of date.

   a. What is the plan for bringing the YP up to date post-Byzantium?

   b. What is the process and ownership for maintaining the YP going forward?

   c. Should updating the YP be made part of the EIP finalisation process?

   d. To facilitate c., Should EIPs be required to include a pull request to the Yellow Paper (if relevant) before they are accepted?

   e. When consensus failures are discovered (e.g. during the recent fuzz testing), how can we make sure that the YP is updated where necessary?

2. If no,

   a. What replaces the YP as the authoritative specification of Ethereum?

   b. Is the YP worth maintaining as a resource that is descriptive rather than prescriptive? If so, the questions above still stand.

[chfast]

New Project: JSON RPC Proxy / eth-agent

1. Discussion: Project idea: HTTP Proxy for JSON-RPC aleth#4563
2. Proof of Concept: https://github.com/chfast/json-rpc-proxy/releases/tag/v0.1.0a1

[pirapira]

Shall we require CC0 notices in EIPs, like:

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).