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
After discussion, I've ended up changing teku to no longer load the local config_name, and we're defaulting the constants that got moved Consensys/teku#7566
It could potentially hide some 'bad config', but the constants that were missing also stopped old config from loading, which is undesirable.
So basically teku when loading:
defaults networking 'constants' that got moved to config
will load preset
then will overlay the remote config onto that
ignores unknown values
in the/eth/v1/config/spec endpoint, we'll be pushing values like GOSSIP_MAX_SIZE (good example of a moved constant) and would hope they're read by the consumer, but at least I'd hope that consumers aren't failing if it's unexpected.
We recently had some interoperability issues when new parameters has been introduced in the configuration.
As an example, when networking parameters has been promoted to configuration parameters caused VCs failing to start if upgraded before their BNs.
In Teku we recently merged a PR making the VC less
choosy
by following the new sequence when consuming/eth/v1/config/spec
:PRESET_BASE
)CONFIG_NAME
) [new]By applying known config by looking up
CONFIG_NAME
, the final configuration is guaranteed to have all expected params.Wrt additional unexpected param (ie. upgrade BN exposing new configs, restart previous VC version) we just print a warning ignoring unknown params.
How are other clients do? If we all agree on a common strategy we could avoid interoperability issues.
The text was updated successfully, but these errors were encountered: