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

ECIP-1084: Hard cap on the gaslimit for the ETC mainnet as an in-protocol consensus rule. #259

Merged
merged 3 commits into from Feb 11, 2020

Conversation

bobsummerwill
Copy link
Member

@bobsummerwill bobsummerwill commented Jan 18, 2020

Hard cap on the gaslimit for the ETC mainnet as an in-protocol consensus rule.

From the block that this ECIP was activated, gaslimit would follow a
curve defined in this proposal rather than being subject to miner voting.

… an in-protocol

consensus rule. From the block that this ECIP was activated, gaslimit would follow a
curve defined in this proposal rather than being subject to miner voting.
@TheEnthusiasticAs TheEnthusiasticAs added the editor:6 enhancement label Jan 18, 2020
@bobsummerwill bobsummerwill self-assigned this Jan 19, 2020
@bobsummerwill
Copy link
Member Author

@bobsummerwill bobsummerwill commented Jan 20, 2020

ECIP Editors: @soc1c @YazzyYaz @meowsbits @sorpaas @BelfordZ:
Please can you review/comment/merge? I think this is ready to go. Thanks!

@soc1c soc1c changed the title Hard cap on the gaslimit for the ETC mainnet as an in-protocol consensus rule. ECIP-1084: Hard cap on the gaslimit for the ETC mainnet as an in-protocol consensus rule. Jan 28, 2020
_specs/ecip-1084.md Show resolved Hide resolved
Copy link
Member

@meowsbits meowsbits left a comment

I'm OK merging from a technical ECIP-draft perspective.

  • Front matter seems in order
  • Formatting and sectioning seems in order

@bobsummerwill
Copy link
Member Author

@bobsummerwill bobsummerwill commented Feb 6, 2020

@meowsbits I see some comments from you in the Discord ecip-github channel but cannot see them here.

Raised from what value to 8M?

What was this in reference to?

This is not obvious to me. My client seems to run fine on ETH, ETC, and test networks. Can you provide benchmarks here?

What was this in reference to?

In general, I am talking about the full-sync from Genesis times for both ETH (which we want to avoid reaching) and ETC. Both time to sync and disk usage.

@bobsummerwill
Copy link
Member Author

@bobsummerwill bobsummerwill commented Feb 8, 2020

You asked "what from" on the gaslimit, @meowsbits?

Here is a historical graph of the ETH gaslimit, which I believe that ETC has pretty much inherited by mistake due to whatever the Parity-Ethereum defaults have been:

https://etherscan.io/chart/gaslimit

The limit was lowered at the time of the Shanghai attacks in Sep/Oct/Nov 2016 or so and you can see a dip in the historical progression there, but you can see in general it was:

3M during 2015
4.7M during 2016 to mid 2017 (barring dip for the attacks)
6.7M mid 2017 to late 2017
8.0M during 2018 and until Sep 2019
10M since Sep 2019.

Full-syncs are horrific now on ETH: https://twitter.com/jgarzik/status/1217488290900848640

See also articles like: https://hackernoon.com/the-ethereum-blockchain-size-has-exceeded-1tb-and-yes-its-an-issue-2b650b5f4f62

@YazzyYaz YazzyYaz merged commit 3eca67c into ethereumclassic:master Feb 11, 2020
1 check passed
@antsankov
Copy link
Contributor

@antsankov antsankov commented May 25, 2020

I think this is a great proposal and look forward to working on it after Phoenix is activated. A few thoughts:

  • I personally like either of the two gas limit functions proposed and believe something that approximates Moore's law - gas limit doubles every 2 years seems like a good target to shoot for.

  • One advantage of this, is that it would allow network participants to provision for "maximum scenario" disk storage requirements. For example:

"I know between now and 2 years from now, a 2mil gas block will be at most 5KB [1], assuming 13second blocks, there will be around 5mil blocks before a gas limit increase. Based on 5KB * 5mil = 25GB. I will only need a 25GB hard disk for the next 2 years"

These numbers are somewhat rooted in reality, but when this gets deployed we should be able to propose this information as a node-operator standard.

Ultimately in favor of this proposal, and looking to see how it progresses.

[1] https://ethgasstation.info/blog/ethereum-block-size/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor:6 enhancement
Projects
ECIP Tracker
  
Awaiting triage
Development

Successfully merging this pull request may close these issues.

None yet

6 participants