🥚
Oval
  • Oval Overview
    • Problem
    • System Overview
  • Integration
    • Quickstart Deployment
    • Morpho Deployment
    • Advanced Deployment
  • Mechanism Details
    • Integration with MEV-Share
    • Mechanism Description
    • Trust Assumptions
    • Oval Update Lifecycle
    • Inclusion Rates
    • Revenue Sharing
  • Contract Architecture
    • Source Adapters
    • Destination Adapters
    • Integration Controllers
    • Oval
    • Gas Profiling
  • Technical Examples
    • Aave Integration
    • Flashbots Integration
  • For Searchers
    • Getting Started
    • Header Specifications
    • Oval Node
  • OEV Data
  • Oval Demo
  • Audit and Bug Bounty
  • Oval Deployments
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Contract Architecture

Destination Adapters

Export Oval prices sourced from an oracle to any desired output interface.

Destination adapters allow Oval to expose prices via any desired output interface. The common case is the Chainlink Destination Adapter. However, in some cases, protocols have other middleware that sits between their contracts and their Oracle. Destination adapters can be used to match whatever interface the protocol uses to access prices.

Other examples can be found here.

PreviousSource AdaptersNextIntegration Controllers

Last updated 9 months ago

Was this helpful?