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
- Decision-relevant evidence: Chainstack’s current documentation index explicitly lists an MEV protection add-on. dRPC’s documentation exposes an MEV protection section and its chain directory advertises Front-Running Protection. These are positive public signals, but today’s captures do not establish mechanism, eligible chains, bundle support, private-mempool architecture, pricing, or guarantees.
- Lifecycle changes/limitations: Blast API is explicitly deprecated and redirects users toward Alchemy. Grove states that it is winding down while Pocket Network continues. LlamaRPC could not be assessed because monitored pages returned HTTP 526 or DNS failures.
- Evidence-quality correction: the living matrix previously contained positive classifications for QuickNode, Alchemy, Infura, NOWNodes, Blast API, and Tatum that were not explicitly supported by the linked monitored pages. Those cells were reset to
Not verified in monitored public evidence(orNot applicable — service deprecatedfor Blast). This does not assert product removal; it removes unsupported inference. - Noise handling: changed hashes/navigation shells on QuickNode, Infura, Chainstack, Ankr, Moralis, NOWNodes, Blockdaemon, Allnodes, and other pages were not treated as market changes unless the extracted text contained a criterion-specific or lifecycle signal.
Topic matrix update
The cumulative brief at topics/private-transactions-mev-protection.md was rebuilt around four uniform dimensions:
- protected/private submission;
- bundles/private orderflow;
- mempool privacy;
- 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
- Checked home, pricing, enterprise, blog, and chains.
- The captured text covers general RPC, developer tooling, enterprise uptime/SLA, throughput, Streams, Webhooks, and chain access, but does not explicitly substantiate protected transaction submission, bundles, mempool privacy, or frontrun/sandwich mitigation.
- Matrix action: four capability cells set to
Not verified in monitored public evidence. - Collection limitation: monitored changelog URL returned 404.
- Diff assessment: page changes appear dominated by navigation/product-shell content; no criterion-specific market change confirmed.
Alchemy
- Checked home, pricing, enterprise, and blog.
- No explicit criterion-specific evidence appeared in the captured surfaces.
- Matrix action: four capability cells set to
Not verified in monitored public evidence. - Collection limitations: monitored chain-reference and customer-story URLs returned 404; these are URL/extraction gaps, not product-negative evidence.
- Change assessment: no detected page-level change on the successful surfaces.
Infura
- Checked home, pricing, networks, and documentation.
- General managed API, archive, throughput, and support claims do not establish private transaction or MEV-protection capability.
- Matrix action: four capability cells remain
Not verified in monitored public evidence. - The old Infura blog route resolves to MetaMask developer news; no criterion-specific claim was taken from it.
Chainstack
- Checked home, pricing, protocols, enterprise, blog, and platform documentation.
- The documentation index explicitly lists “MEV protection” under add-ons. This is sufficient for a narrow positive classification only in the frontrun/sandwich-mitigation column; exact protection mechanism and scope remain unverified.
- Matrix action: frontrun/sandwich mitigation marked
Publicly evidencedwith caveat; protected submission, bundles, and mempool privacy remain unverified. - Diff assessment: broad website changes look like navigation/product-shell refreshes; the durable topic evidence is the docs label, not the changed hash.
Ankr
- Checked home, RPC, enterprise, and documentation.
- Captured evidence covers multichain RPC, enterprise throughput, dedicated infrastructure, and support, but not the four topic dimensions.
- Matrix action: all four cells remain unverified.
- Blog change concerned new posts such as x402/chain support, not this criterion.
Moralis
- Checked home, pricing, chains, enterprise, and documentation.
- Captured surfaces emphasize data APIs, Streams, datasets, feeds, and RPC nodes; no explicit private-transaction or MEV-protection evidence was found.
- Matrix action: all four cells remain unverified.
- Homepage hash change was not treated as a capability change.
NOWNodes
- Checked home, pricing, nodes, and blog.
- Public evidence covers shared/dedicated nodes, archive mode, WebSocket, webhooks, and gRPC, but does not explicitly support private submission, bundles, mempool privacy, or frontrun/sandwich mitigation.
- Matrix action: prior private-transaction positive cell removed; all four cells now unverified.
- Collection limitation: monitored Postman documentation URL returned 404.
dRPC
- Checked home, pricing, documentation, chain directory, and blog.
- Documentation navigation explicitly includes MEV protection, and the chain directory advertises Front-Running Protection.
- Matrix action: frontrun/sandwich mitigation retained as
Publicly evidenced, narrowly phrased; protected submission, bundles, and mempool privacy reset/remain unverified because the snapshot does not establish them. - Change assessment: no page-level change; this is preserved confirmed evidence, not a new launch claim.
Blast API
- Home, pricing, chain, and blog routes all show a service deprecation notice; documentation redirects to Alchemy.
- Matrix action: current capability cells changed to
Not applicable — service deprecatedand the row remains for lifecycle context. - Historical Blast claims are not transferred to Alchemy without direct Alchemy evidence.
Blockdaemon
- Checked home, blog, and documentation.
- Current captured text covers institutional transaction, data, RPC, and dedicated-node services but no explicit topic evidence.
- Matrix action: all four capability cells remain unverified.
- Collection limitation: former
/blockchain-apiand/pricingpaths returned 404; this indicates stale monitored URLs, not absence of Blockdaemon services.
Tatum
- Checked home, pricing, documentation, and blog.
- Smart wallets, transaction signing, gas sponsorship, RPC routing, and RPC access are not equivalent to protected/private submission or MEV mitigation.
- Matrix action: prior MEV/frontrun positives removed; all four cells now unverified.
- Collection limitation: monitored supported-blockchains URL returned 404.
Pocket Network / Grove
- Grove states that it is winding down; Pocket Network continues with an agentic data-services direction.
- No explicit topic evidence was found in the successful captures.
- Matrix action: all four capability cells remain unverified; freshness note now records the Grove/Pocket lifecycle distinction.
- Collection limitation: Grove documentation hostname failed DNS resolution.
LlamaRPC
- Home and chain pages returned HTTP 526; documentation and status hostnames failed DNS resolution.
- Matrix action: all cells remain
Not verified in monitored public evidence, with an explicit collection-unavailable note. - No product-negative conclusion is drawn from fetch failure.
Allnodes
- Checked home, pricing, and help center.
- Current surfaces cover node hosting, archive/full nodes, bare metal, and Solana transaction-landing services, but the capture does not establish the four topic dimensions.
- Matrix action: all four cells remain unverified.
- Collection limitations:
/nodesand/blogreturned 404.
Lava Network
- Checked home, documentation, and blog.
- Decentralized routing, scoring, and failover do not by themselves prove private submission or MEV protection.
- Matrix action: all four cells remain unverified.
- Collection limitations: monitored
/developersand/networkroutes returned 404.
What changed versus what was noise
Confirmed decision-relevant state
- Chainstack: direct documentation label for an MEV-protection add-on.
- dRPC: direct documentation/directory labels for MEV protection and front-running protection.
- Blast API: service deprecated.
- Grove: winding down; Pocket Network continues separately.
- LlamaRPC: current public assessment blocked by HTTP/DNS failures.
Not treated as market change
- Changed hashes on generic home, pricing, blog, enterprise, protocol, or navigation pages without a criterion-specific textual change.
- Generic low-latency, transaction-submission, wallet-signing, routing, archive, WebSocket, webhook, or dedicated-node claims.
- Broken legacy URLs and extraction failures, except as explicit research limitations.
Implications for GetBlock
- Sales: do not accept a vendor’s “MEV protection” label as parity proof. Ask for chain/method scope, relay/builder architecture, public fallback behavior, and contractual guarantees.
- Product marketing: an evidence-backed differentiation opportunity exists if GetBlock can document protected submission precisely—supported chains, privacy model, failure semantics, observability, and pricing—rather than use a broad MEV label.
- Content: publish a technical buyer guide distinguishing private transaction RPC, bundles, low-latency landing, revert protection, frontrunning mitigation, and sandwich protection.
Research gaps and next actions
- Retrieve dedicated Chainstack and dRPC product pages/docs for mechanism, chain scope, bundle support, pricing, and guarantees.
- 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. - Re-test LlamaRPC from an independent network and identify a canonical current docs source.
- Keep Blast API deprecated and evaluate Alchemy independently.
- Verify all volatile claims before external sales use.
Publishing and paper status
- Pre-run encyclopedia publication reported success with 138 URLs and latest daily date
2026-10-16; a post-consolidation rebuild is required so this revised report and matrix reach HTML. - Agentic routing paper updater reported
ok=true,paper_updated=true, with 61 evidence items, and published the living paper at Agentic routing RPC. - Limitation: the updater’s generated note nominated generic QuickNode status/webhook/streams/SLA text as routing-paper evidence. That may inform routing policy and SLA schema, but it is not evidence of private transactions or MEV protection.