Provider API
Providers
Execution providers can use the provider
role to run their nodes. This allows them to receive signed bids and issue commitments for execution.
The Provider RPC API allows providers to receive signed bids that are being propagated in the network.
Once they get a bid, they’ll need to communicate with the mev-commit node to Accept.
Accepted bids result in the mev-commit node sending a signed commitment to the p2p network.
The Provider API is implemented using the gRPC framework, supporting two primary operations:
- Receiving Bids: Providers receive streaming bids from the mev-commit node.
- Sending Processed Bids: Providers send information about processed bids back to the mev-commit node.
RPC API Details
The protobuf file is available in the repository. The Go client has already been generated in the repository. To generate the RPC client for other languages, please follow the instructions in the gRPC documentation.
Primary RPC Operations:
Message Structures
HTTP API
The same API is also available on the HTTP port configured on the node. Please review the API docs to understand the usage.
An example client is implemented in the repository. This example showcases how to integrate a client into the provider’s operational framework. While the sample client automatically accepts every incoming bid, providers should incorporate their own decision-making logic to evaluate and respond to these bids.