Skip to main content

Oracle Security

Current Phase: Shadow Mainnet Testing

Multyr contracts are deployed on Arbitrum One. The system is currently in validation phase. Deposits are not open to the public. Behavior described on this page reflects the protocol's designed behavior; some mechanisms are active in shadow testing, others become active at public launch. See the Status page for details.

Multyr relies on external price feeds for valuation and execution decisions.

The system implements multiple safeguards to ensure oracle integrity.


Oracle Source

Primary data source:

  • Chainlink Aggregators

Accessed via:

  • latestRoundData()
  • on-demand reads (no cached price dependency)

Staleness Protection

Each oracle feed is validated against staleness thresholds:

ParameterValue
Minimum staleness~1 minute
Maximum staleness~24 hours
Default threshold~1 hour

If data exceeds allowed staleness:

  • deposits are blocked
  • strategy operations may halt
  • withdrawals remain available

Secondary Oracle Validation

Optional secondary oracle provides cross-validation.

Mechanism:

  • compare primary and secondary prices
  • compute deviation

If deviation exceeds threshold (~2% default):

→ transaction reverts (OraclePriceMismatch)


Fallback Behavior

ScenarioDepositsWithdrawalsStrategy Ops
Primary staleBlockedAllowedBlocked
Secondary downAllowedAllowedAllowed
Both staleBlockedAllowedBlocked
Deviation exceededBlockedAllowedBlocked

Warm NAV as Secondary Layer

In addition to price feeds, the system uses a warm NAV cache:

  • must be refreshed periodically
  • max age ~15 minutes

If stale:

  • deposit path enforces refresh
  • may revert if invalid
  • withdrawals never blocked

Safety Design

The oracle system is designed to:

  • prevent incorrect pricing
  • avoid forced liquidations
  • ensure safe degradation

Key Guarantees

  • withdrawals are never blocked due to oracle issues
  • deposits are only allowed with valid pricing
  • system avoids acting on invalid data

Summary

Multyr's oracle system combines:

  • primary Chainlink feeds
  • optional secondary validation
  • staleness controls
  • execution guards

ensuring safe and reliable pricing across all operations.