You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.
Using proof-of-stake consensus, a votable system is required for gas limits, block time etc.
Why should this feature exist?
What are the use-cases?
This will allow a governance model for the blockchain, instead of hard-coded parameters and also make it easier to make changes at runtime instead of a hard-fork or requiring client update.
However, post any new voted change, the system should allow a period of at-least 30 days, to give time for validators to update their hardware and network to keep up with gas limit changes.
Implementation
Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?
What is the priority?
(On a scale of 1 to 5, with 1 being highest priority)
The text was updated successfully, but these errors were encountered:
Rationale
Using proof-of-stake consensus, a votable system is required for gas limits, block time etc.
Why should this feature exist?
What are the use-cases?
This will allow a governance model for the blockchain, instead of hard-coded parameters and also make it easier to make changes at runtime instead of a hard-fork or requiring client update.
However, post any new voted change, the system should allow a period of at-least 30 days, to give time for validators to update their hardware and network to keep up with gas limit changes.
Implementation
Do you have ideas regarding the implementation of this feature?
Are you willing to implement this feature?
What is the priority?
(On a scale of 1 to 5, with 1 being highest priority)
The text was updated successfully, but these errors were encountered: