Liquidity Management
Gamma
DeFiFoundry
50,000 USDC
View results
Previous Next
Submission Details
Severity: medium
Valid

Hardcoded Arbitrum Sequencer Feed Address makes protocol incompatible with Avalanche

anchabadze

Description:

The protocol is designed to work on both Arbitrum and Avalanche networks...

Compatibilities:
Blockchains:
- Arbitrum / Avalanche

...but the current implementation has network-specific validation issues.

The KeeperProxy contract has hardcoded the Arbitrum Sequencer Uptime Feed address in the initialize function:

// KeeperProxy.sol
function initialize() external initializer {
__Ownable2Step_init();
sequencerUptimeFeed = AggregatorV2V3Interface(0xFdB631F5EE196F0ed6FAa767959853A9F217697D);
}

This address is specific to Arbitrum network and will not work on Avalanche since Avalanche doesn't use a Sequencer (it's an L1 chain)

Impact:

When deployed on Avalanche:

  • All price validation calls will revert (functions KeeperProxy::run() and KeeperProxy::runNextAction())

  • Keepers won't be able to execute orders

  • Users won't be able to trade

  • The protocol will be completely non-functional

Recommended Mitigation:

Add chain-specific configuration and network-specific validation

Updates

Lead Judging Commences

n0kto Lead Judge 3 months ago
Submission Judgement Published
Validated
Assigned finding tags:

finding_Avalanche_has_no_sequencer

Likelihood: High, run and runNextAction will revert. Impact: Low, any deposit will be retrieve thanks to cancelFlow.

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.