Add feature flags for network protocol level changes. #440
Labels
enhancement
New feature or request
Warp Signature API
API service for serving arbitrary Warp signatures from any VM
Context and scope
Current features being developed such as ACP-118 support #383 depend on network level changes that are present in default branches in upstream repos (
avalanchego
,coreth
andsubnet-evm
).We need to be able to continue developing on top of these new features while also preserving the ability to push hot fixes and new versions to currently deployed instances of relayer.
To do so we need a configuration setting that determines which protocol level of the network is required for given features.
Discussion and alternatives
Alternatives that were proposed were:
Both of these seem more cumbersome and error prone than a re-usable feature flag config settings that defaults to the most recent network version live on mainnet.
The text was updated successfully, but these errors were encountered: