Description
Context and scope
Currently, AvalancheGo will drop connections to any nodes that are not updated when a required network upgrade activates, including relayer and aggregator nodes. However, relayer and aggregator nodes in many cases do not need to be updated since they are not performing consensus or executing any chains.
Evaluate if this requirement can/should be relaxed automatically by relayer/aggregator nodes claiming to be the latest release version so their connections are not dropped by peers. This would remove the need for new relayer/aggregator releases for every Avalanche network upgrade (including those with no breaking changes for the relayer/aggregator)
Discussion and alternatives
Otherwise, new relayer and aggregator releases must be published for all Avalanche network upgrades alongside of AvalancheGo, even if there are no changes in the P2P layer that affect the relayer or aggregator.
Open questions
How to safely know which "version" the relayer/aggregator should claim to be using?