🥚
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. For Searchers

Getting Started

Getting up and running with the Oval Builder.

PreviousFor SearchersNextHeader Specifications

Last updated 11 months ago

Was this helpful?

Connecting to Oval as a searcher is designed to be simple. You simply add a new RPC to your builder config, send your bundles to it, and nothing else needs to change within your code. The Oval Node, which exposed a standard builder RPC, can be found at:

https://rpc.oval.xyz

To this endpoint you can send standard eth_sendBundle eth_callBundlepayloads. eth_cancelBundle and eth_mevBundle are not supported at this time. Bundle structures are expected to be the same as standard MEV-boost eth_sendBundle calls, as documented by . Expected payload is structured as follows:

{
  "method": 'eth_sendBundle',
  "params": [
    {
      "txs": ['0x1234…', '0x4567…'], // Array of signed transactions
      "blockNumber": '0x420', // Hex of target block
    },
  ],
  "id": 1,
  "jsonrpc": '2.0',
}

Note that the canonical structure of eth_sendBundle differs depending on the builder you connect to. If you send bundles to via this endpoint they also support minTimestamp, maxTimestamp ,replacementUuid and revertingTxHashes. If you send bundles to Titan then they support the aforementioned as well as refundPercent, refundRecipient, refundRecipient. If any payload is sent to the Oval RPC containing any of these fields the RPC will return an error.

For header requirements and optional headers, please refer to the section.

For details on how Oval RPC works and why some parameters are not supported seeOval Node.

Flashbots
Flashbots
Header Specifications