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.

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

Ethereum Core Devs Meeting 29 Agenda #27

Closed
Souptacular opened this Issue Nov 29, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@Souptacular
Member

Souptacular commented Nov 29, 2017

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: ethereum/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

This comment has been minimized.

Show comment
Hide comment
@benjaminion

benjaminion Nov 29, 2017

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.

benjaminion commented Nov 29, 2017

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

This comment has been minimized.

Show comment
Hide comment
@chfast

chfast Nov 30, 2017

Contributor

New Project: JSON RPC Proxy / eth-agent

  1. Discussion: ethereum/aleth#4563
  2. Proof of Concept: https://github.com/chfast/json-rpc-proxy/releases/tag/v0.1.0a1
Contributor

chfast commented Nov 30, 2017

New Project: JSON RPC Proxy / eth-agent

  1. Discussion: ethereum/aleth#4563
  2. Proof of Concept: https://github.com/chfast/json-rpc-proxy/releases/tag/v0.1.0a1
@pirapira

This comment has been minimized.

Show comment
Hide comment
@pirapira

pirapira Nov 30, 2017

Member

Shall we require CC0 notices in EIPs, like:

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

pirapira commented Nov 30, 2017

Shall we require CC0 notices in EIPs, like:

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment