The original design of the relayer was to serve as a proxy for many validators. While this is still one use, it is also being used by validators to serve a single identity.
This PR adds the ability to bypass the leader schedule check and forwards all valid (post-sigverify/dedup) packets to any connected leader. This should make the relayer more resilient to network forking.
If testing of this PR is successful, a future PR will remove the dependency on the websocket connection to the validator when this flag is enabled, which will remove the need for --full-rpc-api in the validator for co-hosted setups.
Note: This also updates several dependencies to address security reports from dependabot.
The original design of the relayer was to serve as a proxy for many validators. While this is still one use, it is also being used by validators to serve a single identity.
This PR adds the ability to bypass the leader schedule check and forwards all valid (post-sigverify/dedup) packets to any connected leader. This should make the relayer more resilient to network forking.
If testing of this PR is successful, a future PR will remove the dependency on the websocket connection to the validator when this flag is enabled, which will remove the need for
--full-rpc-apiin the validator for co-hosted setups.Note: This also updates several dependencies to address security reports from dependabot.