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)
🎯 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: