-
Notifications
You must be signed in to change notification settings - Fork 100
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
*: add custom target gas limit in cluster lock v1.10 #3456
base: main
Are you sure you want to change the base?
Conversation
ee9b93a
to
3eba5c2
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3456 +/- ##
==========================================
+ Coverage 56.93% 57.02% +0.09%
==========================================
Files 218 218
Lines 32430 32562 +132
==========================================
+ Hits 18464 18570 +106
- Misses 12071 12087 +16
- Partials 1895 1905 +10 ☔ View full report in Codecov by Sentry. |
3eba5c2
to
609e242
Compare
Quality Gate passedIssues Measures |
Up until now the gas limit was hardcoded to 30M. However, the community is pushing towards bumping those numbers and you can't really customise that in Charon.
With those updates a
targetGasLimit
variable is introduced to the cluster definition and a new version of cluster definition is created, v1.10. The previous default version was v1.8, now the default is set to v1.10, including also the changes of consensus protocol introduced in v1.9. However, good to keep in mind there is only 1 consensus protocol enabled in charon, meaning the consensus protocol configuration in v1.9 isn't making much difference.Previously the gas limit was hardcoded to 30M, now this can be configured by supplying
--target-gas-limit
flag to both CreateDKG and CreateCluster commands. The variable is not compulsory and its default is set to 36M (this is the new value commonly used in the ecosystem). If a new charon version (i.e.: v1.3) uses old definition (and lock) file, its default will still be the previous one of 30M. To bump the number, unfortunately, a new cluster needs to be created with the updated definition version.category: feature
ticket: #3419