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
The community wants to raise the target gas limit. Currently that is not easy to do in Charon.
🛠️ Proposed solution
The challenge here, is trying to coordinate all VCs to sign a higher limit. This is something we attempted early in charon development, and disfavoured over signing a single registration at the point of dkg or key splitting.
To begin, I suggest we stick to the key splitting/dkg moment, but further more realtime approaches may be considered in future.
The suggestion is to include a target_gas_limit field in a new version of the cluster_definition object. With a default of 36m. This could be overridden with the flag --target-gas-limit int The target block gas limit for the cluster (Default: 36000000)
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
🎯 Problem to be solved
The community wants to raise the target gas limit. Currently that is not easy to do in Charon.
🛠️ Proposed solution
The challenge here, is trying to coordinate all VCs to sign a higher limit. This is something we attempted early in charon development, and disfavoured over signing a single registration at the point of dkg or key splitting.
To begin, I suggest we stick to the key splitting/dkg moment, but further more realtime approaches may be considered in future.
The suggestion is to include a
target_gas_limit
field in a new version of the cluster_definition object. With a default of 36m. This could be overridden with the flag--target-gas-limit int The target block gas limit for the cluster (Default: 36000000)
This const https://github.com/ObolNetwork/charon/blob/main/core/validatorapi/validatorapi.go#L36 is what should be parameterized.
Describe the solution to be implemented
🧪 Tests
The text was updated successfully, but these errors were encountered: