Description
Implement an intelligent, high-availability RPC failover mechanism to maintain protocol liveness.
Problem Statement
The engine currently relies on a static RPC provider. If the provider experiences jitter or downtime, the transaction submission stalls, leading to unnecessary delays in task execution and poor user experience for Guardians.
Technical Requirements
- Requirement: Maintain a weighted list of secondary RPC providers.
- Requirement: Implement a health-check monitor that proactively tests endpoints before routing traffic.
Implementation Guide
- Suggested Approach: Create a background task in
src/engine/rpc.rs that maintains a sliding window of successful/failed requests per provider.
- Branch Strategy:
git checkout -b feat/rpc-failover-optimization
- Affected Areas:
src/engine/rpc.rs
Acceptance Criteria
Security & Audit Considerations
Definition of Done
Description
Implement an intelligent, high-availability RPC failover mechanism to maintain protocol liveness.
Problem Statement
The engine currently relies on a static RPC provider. If the provider experiences jitter or downtime, the transaction submission stalls, leading to unnecessary delays in task execution and poor user experience for Guardians.
Technical Requirements
Implementation Guide
src/engine/rpc.rsthat maintains a sliding window of successful/failed requests per provider.git checkout -b feat/rpc-failover-optimizationsrc/engine/rpc.rsAcceptance Criteria
Security & Audit Considerations
Definition of Done