Stream orderflow

SubscribeOrderflow streams every transaction and bundle that touches one of your accounts on its way to the validators. The call needs the orderflow permission.

Subscribe

Send 1 to 1,024 accounts as raw 32-byte public keys. A bundle matches when any of its transactions uses one of them. Accounts loaded from an address lookup table count too.

message SubscribeOrderflowRequest {
  repeated bytes accounts = 1;
}

To test your key, subscribe with grpcurl and the protocol file. grpcurl reads and prints bytes as base64. The account below is the Pump.fun program 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P.

grpcurl -plaintext \
  -proto searcher.proto \
  -H 'x-api-key: YOUR_API_KEY' \
  -d '{"accounts": ["AVbg9pNmWs9E2xVovxdbqlGJy5f10v87ZV0rtv1tGLA="]}' \
  84.32.103.226:11227 \
  inertia.searcher.v1.Searcher/SubscribeOrderflow

Messages

Each Bundles message carries a batch of bundles. A bundle has two fields:

• signature is the 64-byte signature of the first transaction. You bid with this value.
• transactions holds the transactions in execution order. A single transaction arrives as a bundle with one entry.

Each entry is one Solana VersionedTransaction in wire format.

Transactions from the TPU and from Block Engine bundles arrive in the same format. The stream skips vote transactions.

Limits

• Read the stream continuously. When your client falls behind, the node drops batches for your stream.
• Each node serves a limited number of orderflow streams across all searchers. When all are taken, the call fails with RESOURCE_EXHAUSTED.