GetBlock RPC competitor monitor — 2026-10-16

Criterion of the day: Private transactions and MEV protection: protected RPC, bundles, mempool privacy and frontrun/sandwich mitigation (private-transactions-mev-protection).

Executive summary

Topic matrix update

The cumulative brief at topics/private-transactions-mev-protection.md was rebuilt around four uniform dimensions:

  1. protected/private submission;
  2. bundles/private orderflow;
  3. mempool privacy;
  4. frontrun/sandwich mitigation.

All 15 tracked providers are represented. Current breadth is 2/15 with at least one directly evidenced capability dimension, and 0/15 complete across all four dimensions. Blast API is retained as a deprecated lifecycle row rather than counted as a current capability provider.

Evidence by provider

QuickNode

Alchemy

Infura

Chainstack

Ankr

Moralis

NOWNodes

dRPC

Blast API

Blockdaemon

Tatum

Pocket Network / Grove

LlamaRPC

Allnodes

Lava Network

What changed versus what was noise

Confirmed decision-relevant state

Not treated as market change

Implications for GetBlock

Research gaps and next actions

  1. Retrieve dedicated Chainstack and dRPC product pages/docs for mechanism, chain scope, bundle support, pricing, and guarantees.
  2. Run narrow first-party documentation searches for eth_sendPrivateTransaction, eth_sendBundle, private relay, protected RPC, frontrunning, and sandwich across the 11 assessable providers with no positive evidence.
  3. Re-test LlamaRPC from an independent network and identify a canonical current docs source.
  4. Keep Blast API deprecated and evaluate Alchemy independently.
  5. Verify all volatile claims before external sales use.

Publishing and paper status