Reclaim documentation

Everything you need to integrate, use, and build on the Reclaim MEV Protection Protocol.

Overview

Reclaim is a full-stack MEV protection protocol for Ethereum. It shields your transactions from sandwich attacks, captures MEV that bots would extract, and returns 80% of captured value directly to your wallet.

The protocol consists of four products, each building on the previous:

Quick start

Get protected in under 30 seconds. No account, no sign-up, no fees.

MetaMask setup

Automatic (recommended)

Click the "Protect my wallet" button on our website. This calls wallet_addEthereumChain and configures MetaMask automatically.

Manual setup

Open MetaMask → Settings → Networks → Add Network → Add a network manually:

Other wallets

Any wallet that supports custom RPC endpoints works with Reclaim. This includes Rabby, Rainbow, Coinbase Wallet, Trust Wallet, and Frame. Simply add https://rpc.reclaimfi.xyz as a custom Ethereum RPC.

How it works

The MEV problem

When you submit a transaction on Ethereum, it enters the public mempool — a waiting area visible to everyone. MEV bots monitor this mempool and exploit your transactions through:

• Sandwich attacks: A bot places a buy order before yours and a sell order after, profiting from the price movement your trade creates.
• Front-running: A bot copies your transaction with a higher gas price, executing the same trade before you at a better price.
• Back-running: A bot places a trade immediately after yours to capture arbitrage created by your transaction's price impact.

The Reclaim solution

Reclaim operates a three-layer defense:

1. Private routing: Your transaction is sent to a private mempool via Flashbots Protect infrastructure. MEV bots cannot see it in the public mempool, eliminating sandwich attacks entirely.
2. Value capture: When your transaction creates legitimate arbitrage opportunities (back-running), Reclaim's engine captures this value instead of letting random bots take it.
3. Rebate distribution: 80% of captured MEV is returned to your wallet through our on-chain rebate smart contract. The remaining 20% covers infrastructure costs.

Reclaim RPC Live

The Reclaim RPC is a JSON-RPC proxy that intercepts eth_sendRawTransaction calls and routes them through private infrastructure. All other RPC methods are forwarded to a standard Ethereum node.

Endpoint

https://rpc.reclaimfi.xyz

Supported methods

All standard Ethereum JSON-RPC methods are supported. The RPC is fully compatible with MetaMask, ethers.js, web3.js, viem, and any Web3 library.

Rate limits

The RPC has no artificial rate limits for standard usage. High-frequency programmatic access (>100 requests/second) may be throttled. Contact us for enterprise access.

Reliability

The RPC proxy runs on dedicated infrastructure with automatic failover. If the private routing path is unavailable, transactions fall back to standard Ethereum submission. Uptime target: 99.9%.

Reclaim Swap Q2 2026

Reclaim Swap is a DEX aggregator that routes trades through the optimal path across Uniswap, Curve, Balancer, SushiSwap, and other venues. Unlike standard aggregators, Reclaim Swap captures MEV created by your trade and returns it as cashback.

How it differs from other aggregators

• Intent-based execution: You sign an intent (what you want to trade), not a specific transaction. This allows the protocol to find the optimal execution path at the moment of inclusion.
• MEV cashback: Standard aggregators route your trade and keep any MEV it creates. Reclaim captures it and returns 80% to you.
• Gasless swaps: Using EIP-2612 permit signatures, you can trade without holding ETH for gas. The protocol covers gas from MEV proceeds.

Reclaim Wallet Q3 2026

A Chrome extension wallet with native MEV protection built into every transaction — not just swaps. Transfers, approvals, contract interactions, NFT mints — everything flows through Reclaim's private routing.

Planned features

• Transaction simulation with risk alerts before signing
• Built-in earnings dashboard showing accumulated rebates
• Referral rewards tracking and management
• Multi-chain support (Ethereum, Arbitrum, Optimism, Base)
• Account abstraction support (ERC-4337)

Infrastructure Q4 2026

The final layer: Reclaim operates its own block builder, relay, and validator infrastructure. This captures MEV at every level of the Ethereum stack — from user intent to block inclusion — and returns maximum value to the ecosystem.

Vertical integration

By controlling the full stack, Reclaim can capture 90-100% of MEV from its orderflow (compared to 40-60% when relying on third-party builders). The majority is returned to users through the rebate contract.

Architecture

System overview

Data flow

1. User submits transaction via MetaMask (configured with Reclaim RPC)
2. RPC proxy decodes the transaction to identify swap parameters
3. Transaction is forwarded to Flashbots Protect (private mempool)
4. MEV engine evaluates backrun opportunities against the user's swap
5. If profitable: backrun bundle is submitted alongside the user's transaction
6. User's transaction executes at the expected price (no sandwich)
7. Backrun profit is accumulated in the rebate contract
8. Periodic batch distribution sends 80% to users, 20% to protocol

API reference

RPC endpoint

POST https://rpc.reclaimfi.xyz

Standard JSON-RPC 2.0. All Ethereum methods supported.

Stats endpoint

GET https://rpc.reclaimfi.xyz/stats

Returns protocol statistics. No authentication required.

Response

{
  "total_requests": 142857,
  "total_txs_protected": 8421,
  "total_mev_captured_wei": "1250000000000000000",
  "total_rebates_paid_wei": "1000000000000000000",
  "active_users": 347
}

Health endpoint

GET https://rpc.reclaimfi.xyz/health

Returns 200 if the RPC proxy is operational.

Smart contract

Rebate distributor

The rebate contract handles all MEV distribution to users. It is deployed on Ethereum mainnet and is fully verifiable on Etherscan.

Key functions

Security

Trust model

Reclaim operates with minimal trust assumptions:

• Transaction privacy: Relies on Flashbots Protect infrastructure, which is battle-tested with millions of transactions. Reclaim does not store or log transaction data.
• Rebate honesty: The rebate contract is on-chain and verifiable. Users can independently verify that distributions match captured MEV. The protocol cannot take more than the declared 20% share.
• RPC availability: If the Reclaim RPC is unavailable, MetaMask automatically falls back to the default Ethereum RPC. No transactions are lost or delayed beyond normal network conditions.

What Reclaim can and cannot do

Open source

The full codebase is available on GitHub. We encourage security researchers to review the code and report vulnerabilities.

Responsible disclosure

If you discover a security vulnerability, please report it to contact@reclaimfi.xyz. We take all reports seriously and will respond within 24 hours.

Referral program

Earn passive income by inviting others to use Reclaim. When your referrals earn MEV rebates, you receive 5% of their rebates — automatically, on-chain, forever.

How it works

1. Connect your wallet on reclaimfi.xyz
2. Copy your unique referral link: reclaimfi.xyz/?ref=0xYOUR_ADDRESS
3. Share with friends, communities, Twitter — anyone who trades on Ethereum
4. When they add Reclaim RPC and start trading, their referral is registered on-chain
5. Every time they earn rebates, 5% is automatically distributed to your wallet

Economics

FAQ

Is Reclaim free?

Yes. There are no fees to use the Reclaim RPC. The protocol earns revenue from the 20% share of captured MEV, which would otherwise go to random bots. You pay nothing extra — you actually earn money you would have lost.

Does Reclaim work with all dApps?

Yes. Any Ethereum dApp that works with MetaMask works with Reclaim. Uniswap, Aave, Curve, OpenSea, 1inch, Balancer — all compatible. The RPC is a transparent proxy that doesn't interfere with normal Ethereum operations.

Will my transactions be slower?

Transactions routed through Flashbots Protect typically land within 1-3 blocks (12-36 seconds), similar to standard submission. In rare cases of network congestion, private transactions may take slightly longer as they don't compete on gas price in the public mempool.

What if the Reclaim RPC goes down?

MetaMask stores multiple RPC endpoints. If the Reclaim RPC is unavailable, you can switch to your default Ethereum RPC (Infura, Alchemy, etc.) with one click. No funds are at risk.

How are rebates calculated?

When your transaction creates a backrun opportunity (arbitrage from the price impact of your swap), the protocol captures this value via an atomic flash loan transaction. 80% of the profit from this backrun is allocated to your wallet. Rebates are accumulated and distributed in batches to minimize gas costs.

Can I verify my rebates on-chain?

Yes. The rebate smart contract is deployed on Ethereum mainnet and verified on Etherscan. You can call getUserStats(yourAddress) to see your total rebates, referral earnings, and referral count.

Is Reclaim open source?

Yes. The complete source code is available at github.com/reclaim-rpc/reclaim-fi. We believe transparency is essential for trust in DeFi infrastructure.

How is Reclaim different from Flashbots Protect?

Flashbots Protect provides private transaction routing and some MEV refunds. Reclaim builds on top of Flashbots infrastructure and adds: active MEV capture through a dedicated backrun engine, an on-chain rebate contract with 80% user share, a referral program, and a roadmap toward a full-stack MEV protocol (DEX, wallet, builder).

How is Reclaim different from MEV Blocker?

MEV Blocker (by CoW Protocol) returns 90% of backrun value to users. Reclaim returns 80% but offers a broader product suite: upcoming DEX aggregator, browser wallet, and full vertical infrastructure. MEV Blocker is an RPC endpoint; Reclaim is a protocol ecosystem.

Contributing

Reclaim is open source and welcomes contributions from the community.

Repository

git clone https://github.com/reclaim-rpc/reclaim-fi.git

Development setup

1. Clone the repository
2. Install dependencies: pip install -r requirements.txt
3. Copy .env.example to .env and configure
4. Run locally: python rpc_proxy.py
5. Submit PRs to the master branch

Areas for contribution

• Additional DEX router decoders (decode swap calldata from new aggregators)
• Multi-chain support (Arbitrum, Optimism, Base RPC proxying)
• Dashboard improvements and new data visualizations
• Documentation improvements and translations
• Security reviews and vulnerability reports