Add L2 Sequencer Health Check for Chainlink Feeds (If Applicable) #108
Description
Description
As a contract developer, I want to incorporate checks for L2 sequencer availability when retrieving Chainlink price feeds if the contract is deployed on an L2 network, so that the system avoids using potentially stale prices caused by sequencer downtime.
Acceptance Criteria
- Determine if the contract's target deployment chains include L2 networks supported by Chainlink's L2 Sequencer Uptime Feed.
- If deployed on a relevant L2, integrate checks against the appropriate Chainlink L2 Sequencer Uptime Feed contract before trusting price data from the main Aggregator feed.
- The check should confirm the sequencer is currently reported as active (
isSequencerUp()or similar method provided by the Uptime Feed). - The transaction reverts or handles the sequencer downtime scenario appropriately if the sequencer is reported as down.
Test Cases
- (Requires L2 test environment or mocking) Test price retrieval when the L2 Sequencer Uptime Feed reports the sequencer is UP: ensure price retrieval proceeds normally (subject to standard staleness checks from Ticket 9).
- Test price retrieval when the L2 Sequencer Uptime Feed reports the sequencer is DOWN: ensure the transaction reverts or handles the situation as designed, preventing use of potentially stale prices.
Technical Validation
- Verify if L2 deployment is planned/supported.
- Confirm correct integration with the Chainlink L2 Sequencer Uptime Feed for the specific L2 network(s). (Addresses can be found in Chainlink documentation).
- Ensure the check on sequencer status is performed alongside the standard price feed staleness checks (Ticket 9).
- Review Chainlink's L2 documentation for the recommended integration pattern.