Private Mempool: MEV Protection & Hidden Transactions

We've encountered cases where a client's arbitrage bot lost up to 30% of its profit (approx. $15,000/month) due to front-running: public transactions were intercepted by MEV bots that set higher gas and grabbed liquidity. After implementing a private mempool for private Ethereum transactions based on a Flashbots relay, losses dropped to 2-5%, saving about $10,000/month, and the setup paid for itself in one month. The main cause of losses is the transparency of the public mempool: any unconfirmed transaction is visible to all network nodes. MEV bots analyze it and insert their own transactions before yours, capturing the profit.

Over five years, we have delivered more than 30 projects for transaction protection on Ethereum, Polygon, BNB Chain, and other EVM networks. Our experience shows that a properly configured private mempool can reduce MEV-related losses by up to 90%.

Why a Private Mempool Protects Better Against MEV

A private mempool sends the transaction directly to a block builder, bypassing the public broadcast. The builder includes it in a block without prior disclosure. This blocks the three main MEV attacks:

• Sandwich attack: the bot cannot see your transaction and thus cannot insert a buy before and a sell after.
• Liquidation front-running: the liquidator cannot intercept your position on Aave/Compound.
• Arbitrage pre-emption: arbitrageurs cannot react to your trades within the block.

This provides front-running prevention and sandwich attack protection.

Comparison of Private Submission Solutions

Flashbots Protect is 10 times faster than the public mempool in inclusion time—on average, a transaction lands in the next block. Additionally, gas savings from bundle optimization reach 20%, and average monthly savings from MEV reduction are $5,000–$10,000.

How to Configure a Private Mempool in 5 Steps

1. Choose a Flashbots relay. For a quick start, use Flashbots Protect RPC. Change the endpoint in your code or wallet.
2. Integrate via ethers.js. Connect the provider to https://rpc.flashbots.net. All transactions now go through the private Ethereum RPC channel.
3. For bundle submission, form a bundle (for complex operations). Assemble a sequence of transactions, sign them with @flashbots/ethers-provider-bundle, and submit with a target block number.
4. Set up coinbase payment. Include an ETH transfer to the builder's address in the bundle; the tip size determines priority. This is an anti-MEV measure. Typical fee is 1-5% of the operation's profit.
5. Submit in parallel to multiple relays to increase inclusion reliability.
6. Monitor inclusion rate. Track the percentage of successful inclusions within the target block ± 2.

Key Metrics to Track After Setup

After implementation, we typically see the following improvements:

• Inclusion rate increases from 70-80% to 95%+.
• MEV savings — loss reduction of 80-90% (typical monthly savings of $5,000–$20,000).
• Gas efficiency — bundles use 15-25% less gas due to order optimization.
• ROI on setup is 2-3 months for projects with transaction volumes above $50k/day.

Deliverables: What You Get

We handle private RPC setup for your dApp or bot — turnkey. Our package includes:

• Analysis of your transaction flow and selection of the optimal relay (Flashbots, MEV Blocker, or a custom relay).
• Integration of SDKs (ethers.js, viem, web3.py) with code documentation and examples.
• Configuration of MEV-Boost on your validator (if you run your own staking).
• Optimization of gas parameters and coinbase payment for maximum inclusion rate.
• Deployment of Grafana monitoring with metrics for losses and savings.
• Training for your team: a workshop on bundle and nonce management.
• SLA: incident response time of 2 hours during business hours.

We will evaluate your project for free — contact us via Telegram or email. To order a private mempool configuration, get in touch for a consultation.

Why Order the Setup from Us?

We have been working with blockchain for over five years, delivering more than 30 solutions for MEV protection for DeFi protocols and arbitrage bots. Our engineers are authors of open-source transaction protection tools. We guarantee gas savings of up to 20% thanks to bundle optimization.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.