package block_engine
Get desktop application:
View/edit binary Protocol Buffers messages
/ Relayers can forward packets to Block Engines. / Block Engines provide an AccountsOfInterest field to only send transactions that are of interest.
rpc StartExpiringPacketStream (stream , stream )
block_engine.proto:120Validators can subscribe to packets from the relayer and receive a multiplexed signal that contains a mixture of packets and heartbeats. NOTE: This is a bi-directional stream due to a bug with how Envoy handles half closed client-side streams. The issue is being tracked here: https://github.com/envoyproxy/envoy/issues/22748. In the meantime, the server will stream heartbeats to clients at some reasonable cadence.
message
block_engine.proto:58Packets and heartbeats are sent over the same stream. ExpiringPacketBatches have an expiration attached to them so the block engine can track how long it has until the relayer forwards the packets to the validator. Heartbeats contain a timestamp from the system and is used as a simple and naive time-sync mechanism so the block engine has some idea on how far their clocks are apart.
oneof msg
batches = 1
heartbeat = 2
message
block_engine.proto:65optional heartbeat = 1
rpc SubscribeAccountsOfInterest (, stream )
block_engine.proto:111/ The block engine feeds accounts of interest (AOI) updates to the relayer periodically. / For all transactions the relayer receives, it forwards transactions to the block engine which write-lock / any of the accounts in the AOI.
message
block_engine.proto:33(message has no fields)
message
block_engine.proto:34repeated string accounts = 1
rpc SubscribeProgramsOfInterest (, stream )
block_engine.proto:113message
block_engine.proto:38(message has no fields)
message
block_engine.proto:39repeated string programs = 1
/ Validators can connect to Block Engines to receive packets and bundles.
Block builders can optionally collect fees. This returns fee information if a block builder wants to collect one.
message
block_engine.proto:20(message has no fields)
message
block_engine.proto:21string pubkey = 1
uint64 commission = 2
commission (0-100)
Get list of Block Engine Endpoints (global and regioned) to find the optimal region.
message
block_engine.proto:70Request a list of block engine endpoints to communicate with.
(message has no fields)
message
block_engine.proto:81Response message containing both global and regioned endpoints.
optional global_endpoint = 1
Global endpoint that automatically routes to the closest block engine.
repeated regioned_endpoints = 2
List of regioned endpoints the client can connect to.
rpc SubscribeBundles (, stream )
block_engine.proto:95/ Validators can subscribe to the block engine to receive a stream of simulated and profitable bundles
message
block_engine.proto:15(message has no fields)
message
block_engine.proto:16repeated bundles = 1
rpc SubscribePackets (, stream )
block_engine.proto:92/ Validators can subscribe to the block engine to receive a stream of packets
message
block_engine.proto:9(message has no fields)
message
block_engine.proto:10optional header = 1
optional batch = 2
message
block_engine.proto:28repeated string accounts = 1
use * for all accounts
message
block_engine.proto:73Represents a block engine endpoint with both a URL and a shredstream receiver address.
Used in:
string block_engine_url = 1
Block Engine HTTP URL, eg. `https://mainnet.block-engine.jito.wtf`
string shredstream_receiver_address = 2
Shredstream Receiver Address (hostname with port), eg. `shredstream.mainnet.block-engine.jito.wtf:1002`
message
block_engine.proto:47A series of packets with an expiration attached to them. The header contains a timestamp for when this packet was generated. The expiry is how long the packet batches have before they expire and are forwarded to the validator. This provides a more censorship resistant method to MEV than block engines receiving packets directly.
Used in:
optional header = 1
optional batch = 2
uint32 expiry_ms = 3