SecureRPC

SecureRPC Relay

Overview

MEV-Boost Relay API specification v1. A relay has several core responsibilities:

  • APIs for proposers, block builders and data transparency
  • Handling validator registrations and block proposals in a scalable manner
  • Block escrow, data availability, redundancy
  • Simulate and verify blocks sent by block-builders, rate-limit if necessary

Data Types

Reference implementation of data types with correct SSZ encoding and signing routines can be found in the go-boost-utils repository.

Core Types

  • ValidatorRegistration
  • SignedBuilderBid
  • SignedBlindedBeaconBlock
  • ExecutionPayload

API Endpoints

Proposer API

  • POST `/eth/v1/builder/validators`- Register validator
  • GET `/eth/v1/builder/header/slot/parent_hash/pubkey`- Get execution payload header
  • POST `/eth/v1/builder/blinded_blocks`- Submit signed blinded block

Builder API

  • GET `/relay/v1/builder/validators`- Get validator registrations
  • POST `/relay/v1/builder/blocks`- Submit new block

Data API

  • GET `/relay/v1/data/bidtraces/proposer_payload_delivered`- Get delivered payload BidTraces
  • GET `/relay/v1/data/bidtraces/builder_blocks_received`- Get received builder blocks
  • GET `/relay/v1/data/validator_registration`- Get validator registration status