Active

Update HAIVELO v1 and VELO collateral oracles


Proposal ID

489090...6426

Proposed

Nov 16th, 2026

Result details

4 addresses

66.38K votes

Current Votes

Quorum

66.38K of 48.7K

Majority support

Yes

For

66.38K

Against

12.26K

Abstain

0

Actions

Type

Address

Details

Custom

0x6270...b3A6

modifyParameters(..)

Custom

Account

0x6270...b3A6

Method

modifyParameters(..)

Custom

0x6270...b3A6

modifyParameters(..)

Custom

Account

0x6270...b3A6

Method

modifyParameters(..)

Proposal

This proposal updates the existing HAIVELO (v1) and plain VELO collateral types to the same delayed oracle selected for HAIVELOV2: 0x218f50d4c22ff7c8c5eb627ce63acdb80bb253a4.

The underlying price feed uses AERO/USD multiplied by 0.044, expressed in USD per legacy VELO-denominated collateral unit. It does not value a legacy unit as one whole AERO and does not add a treasury-rebase or NAV multiplier.

Deployment prerequisite

The delayed oracle deployment proposal 4332327879094392726255374129819366225366046619107863927110403276312164812331 must execute first. Before executing this proposal, verify that 0x218f50d4c22ff7c8c5eb627ce63acdb80bb253a4 is the intended DelayedOracleFactory child, with priceSource 0x8b96faa7f377c5a8d500783f1add08092da60f47, updateDelay 3600 seconds and valid current/next prices. Do not execute if these checks fail.

Proposed actions

Call OracleRelayer.modifyParameters(bytes32,bytes32,bytes) on 0x6270403b908505f02da05be5c1956abb59fdb3a6 twice:

  • collateralType: HAIVELO; parameter: oracle; value: 0x218f50d4c22ff7c8c5eb627ce63acdb80bb253a4.
  • collateralType: VELO; parameter: oracle; value: 0x218f50d4c22ff7c8c5eb627ce63acdb80bb253a4.

ETH value is zero for both actions. This proposal does not change debt ceilings, stability fees, safety or liquidation ratios, collateral adapters, token custody or outstanding debt. It does not migrate existing SAFEs to a new token. The valuation change reaches stored SAFEEngine prices only when each collateral type is explicitly relayed. The mandatory operational prerequisite below applies; this proposal is not a guarantee against future liquidations or auction slippage.

Mandatory operational prerequisite before execution

This proposal MUST NOT be executed until a shared-oracle fan-out update path is implemented and verified: advance the shared delayed oracle once, then publish its current quote separately for HAIVELO, HAIVELOV2 and VELO via OracleRelayer.updateCollateralPrice for each collateral type.

The currently deployed OracleJob advances the delayed oracle before relaying only one collateral type. With a shared delayed oracle, subsequent per-collateral jobs can revert on the shared update delay and leave other SAFEEngine prices stale; the current local keeper rejects partial-success batches. Merely changing these oracle pointers, deduplicating jobs, restarting a keeper, or adding a one-time price refresh does not solve recurring updates.

Before execution, independently verify recurring updates, publication for all three collateral types, validity/freshness handling, failure/recovery behavior, and keeper costs/rewards. This prerequisite is an explicit governance/operational condition in the proposal text, NOT an on-chain enforcement condition in these two setter calls. This proposal does not deploy, modify, fund or authorize a keeper implementation. Such implementation and its required operational authorization are separate. If the prerequisite is not met, do not queue/execute this proposal.

Current Votes

Quorum

66.38K of 48.7K

Majority support

Yes

For

66.38K

Against

12.26K

Abstain

0

Current Votes

4 addresses

66.38K votes

Status

Mon Nov 16, 05:03 pm

Published onchain

Tue Nov 17, 05:03 am

Voting period started

Sun Nov 22, 05:03 am

End voting period

Queue proposal

Execute proposal