Proposal: RedStone Oracle Integration and Resilient Oracle Configuration Updates

Venus Governance Venus - Governance Proposals
1

Summary

If approved, this VIP will:

  • Integrate RedStone as an additional oracle provider across multiple assets
  • Enhance multi-vendor redundancy using Chainlink, Binance, and RedStone
  • Improve fallback coverage for BTCB, TRX, and USD1
  • Strengthen price validation mechanisms with updated configurations and validators
  • Continue the rollout of the Two-Vendor OEV Integration Framework to improve protocol resilience

These changes aim to increase oracle reliability, reduce single-source dependency, and enhance the overall safety of the Venus Protocol.

Description

This proposal aims to strengthen price reliability and improve oracle redundancy on the BNB Chain Core Pool by introducing additional oracle sources and updating existing configurations.

As part of ongoing risk management improvements, this proposal continues the Two-Vendor OEV Integration Framework adopted in VIP-586, expanding multi-vendor coverage and enhancing fallback mechanisms across supported assets.

The changes focus on:

  • Introducing RedStone as an additional oracle provider for multiple assets
  • Updating Resilient Oracle configurations to ensure redundancy across Chainlink, Binance, and RedStone
  • Adding fallback oracle support for selected assets to improve system robustness
  • Enhancing validation mechanisms where required

These updates are designed to reduce reliance on any single oracle provider and improve protocol resilience against price discrepancies or oracle failures.

Changes

1. RedStone Oracle Feed Registration

Register 13 new RedStone price feeds with a 7-hour stale period:

  • XVS
  • LTC
  • BCH
  • DOT
  • LINK
  • DAI
  • FIL
  • DOGE
  • AAVE
  • UNI
  • FDUSD
  • TWT
  • SOL

2. Resilient Oracle Configuration Updates

Update configurations for 12 standard assets:

  • MAIN: Chainlink
  • PIVOT: Binance
  • FALLBACK: RedStone

3. Asset-Specific Oracle Configurations

  • TWT
    • MAIN: Binance
    • PIVOT: RedStone
    • (No Chainlink USD feed available)
  • USDe
    • MAIN: Chainlink (via USDT)
    • PIVOT: Chainlink
    • FALLBACK: RedStone

4. Bound Validator Update

  • Add BoundValidator configuration for TWT, as it previously did not have a PIVOT oracle

5. Fallback Oracle Enhancements

Introduce or update fallback oracle configurations for:

  • BTCB
    • MAIN: Chainlink
    • PIVOT: RedStone
    • FALLBACK: Binance
  • TRX
    • MAIN: Chainlink
    • PIVOT: RedStone
    • FALLBACK: Binance
  • USD1
    • MAIN: RedStone
    • PIVOT: Chainlink
    • FALLBACK: Binance

6. Binance Oracle Configuration

  • Symbol override: BTCB → BTC
  • Stale period configuration:
    • BTC: 25 minutes
    • TRX / USD1: 25 hours

We welcome community feedback on this proposal ahead of submitting it for a VIP vote.

1 Like