Skip to content
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 39 Agenda #43

Closed
Souptacular opened this issue May 22, 2018 · 8 comments
Closed

Ethereum Core Devs Meeting 39 Agenda #43

Souptacular opened this issue May 22, 2018 · 8 comments

Comments

@Souptacular
Copy link
Contributor

Souptacular commented May 22, 2018

Ethereum Core Devs Meeting 39 Agenda

Meeting Date/Time: Friday 06/01/18 at 14:00 UTC

Meeting Duration 1.5 hours

YouTube Live Stream Link

Livepeer Live Stream Link

Agenda

  1. Testing & EIP 1085: Common genesis.json format scheme across all client implementations
  2. Client Updates
  3. Research Updates
  4. EIP 1087: Net gas metering for SSTORE operations
  5. Concerns that using native browser VMs for running eWasm is not DoS hardened. See this comment and this comment.
  6. Constantinople hard fork timing and what to include (continuing conversation from last call).
  7. Testnet rent. See this comment.

Please provide comments to add or correct agenda topics.

@karalabe
Copy link
Member

I'd like to request a small discussion around blockchain rent in the context of test network spam.

Generally chain rent is brought up in the context of mainnet, where people debate whether crypto kitties (and similar large contracts) should be allowed to pose large storage overhead on full nodes indefinitely. There are ups and downs around introducing rent and a lot of complexity to go with it, so it's a hard topic to solve. That said, there's a certain runway available since large contracts still have to incur considerable costs to get the data in in the first place.

This runway however breaks down for the test networks. I can't speak for Ropsten or Kovan, but on Rinkeby there are many contracts with over 10MB of data, and at least one instance with 82MB of compressed storage. These black swan contracts pose enormous overheads on synchronization, thus limiting the usefulness of the test networks for the entire ecosystem.

I'm wondering if we could figure out a possible solution (perhaps a limited form of chain rent, or perhaps other limitations on contract storage) that might help keep abuses more manageable.

@mkalinin
Copy link
Contributor

mkalinin commented Jun 1, 2018

Please, fix the link to EIP 1087 in agenda

@gcolvin
Copy link

gcolvin commented Jun 1, 2018

PR by @cdetrio about Wasm "compiler bombs" is here: ewasm/design#99

@Daft-Wullie
Copy link

Daft-Wullie commented Jun 1, 2018

@lrettig
Please, update the youtube/livepeer livestream links so it can be posted on r/ethereum and other community channels to give people interested in listening a little heads up.
Thanks!

@jamesray1
Copy link
Contributor

jamesray1 commented Jun 1, 2018

I'm too busy to attend yet another (third) meeting to propose EIP 908. If people want to seriously consider it they can read it, give feedback and help improve it if necessary, without me having to coax them to give feedback.

https://eips.ethereum.org/EIPS/eip-908

@lrettig
Copy link
Contributor

lrettig commented Jun 1, 2018

Fixed link and posted streaming links. @jamesray1 it sounds like you don't want me to add 908 to the agenda for this call, let me know if I misunderstood.

@jamesray1
Copy link
Contributor

jamesray1 commented Jun 1, 2018

@Souptacular, I won't be attending the meeting, but people are welcome to read the EIP and leave a comment on the discussions-to link.

@lrettig
Copy link
Contributor

lrettig commented Jun 1, 2018

Closing in favor of #44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants