search
ArticlesGuidesDocs

Protocol Integration

Integrate your protocol with Toby's OpenMEV infrastructure to protect users from harmful MEV, earn rebates, and access real-time data feeds.

Protect your users from sandwich attacks, earn MEV rebates, and plug into real-time blockchain data. This guide walks through how protocols and DApps can integrate with Toby's OpenMEV infrastructure.

hashtag
Why Integrate?

Every trade on your protocol is a potential target for MEV extraction. Sandwich bots front-run and back-run user swaps, silently worsening execution quality. Most users never notice. They just get worse prices and eventually leave.

Toby fixes this at the infrastructure level, not at the wallet or RPC layer.

What your protocol gets:

  • MEV protection by default. Block Chef filters sandwich attacks and other harmful patterns before they reach the block. Your users get better prices without changing anything about how they interact with your protocol.

  • MEV rebates. A portion of MEV revenue generated through your protocol's transaction flow is returned to you. This creates a new, passive revenue stream tied directly to your volume.

  • Real-time data via OtterFlow. Access Laser Stream for live transaction data, DEX events, liquidation triggers, and account state changes. Build smarter protocol features on top of actual market activity.

  • Governance participation. Through the OpenMEV Council, your protocol gets a voice in shaping MEV filtering rules. $TOBY holders vote on what strategies are allowed or blocked across the network.

hashtag
Integration Paths

hashtag
1. OpenMEV Protection

Connect your protocol to Toby's block-building pipeline. Once connected, transactions flowing through your contracts are automatically screened by Block Chef's two-layer system:

  • Head Chef inspects incoming bundles and rejects harmful patterns (sandwiches, front-running).

  • Sous Chef runs a fair auction on the remaining bundles and assembles the final block proposal.

You can also define allow-list hooks for your contracts. Want arbitrage (which corrects prices) but not sandwiching (which hurts users)? Set those rules through the OpenMEV Council governance framework. The filtering is granular and community-governed.

hashtag
2. MEV Rebate Program

Protocols generating significant transaction volume can participate in Toby's rebate program. A share of MEV tips collected from searcher bundles that interact with your contracts flows back to your protocol. The rebate percentage scales with volume and integration depth.

Toby charges a 5% protocol fee on MEV rewards. Rebates are calculated from the remaining pool and distributed programmatically.

hashtag
3. Data Feeds via OtterFlow

OtterFlow's Laser Stream is Toby's optimized data layer. It refines raw blockchain data into actionable signals with 30-50% lower hardware requirements than running your own firehose.

Available data includes:

  • Real-time transaction streams with decoded instruction data

  • DEX swap events across Raydium, Orca, Meteora, and other major Solana DEXs

  • Account state change monitoring

  • Lending protocol liquidation triggers (Solend, Marginfi, Kamino)

Both WebSocket (streaming) and REST API (historical queries) connections are supported. Authentication uses an API key via the X-Toby-Key header.

hashtag
Getting Started

Integration is lightweight. Here's the path from first contact to live protection:

  1. Join the Discord at discord.gg/tobyarrow-up-right and request devnet access in the #builders channel.

  2. Connect to Block Chef on devnet. Test your protocol's transaction flow through Toby's filtering layer. Verify that user transactions pass through cleanly while harmful MEV is blocked.

  3. Configure allow-list hooks. Define which MEV strategies can interact with your contracts. This is done through the OpenMEV Council governance interface.

  4. Integrate OtterFlow data feeds (optional). Connect to Laser Stream for real-time market intelligence to power analytics, monitoring, or protocol features.

  5. Go live on mainnet. Once testing is complete, migrate your integration to the mainnet environment.

Note: API endpoints, SDK packages, and full technical documentation will be published at mainnet launch. Devnet access is available now through Discordarrow-up-right.

Related:

PreviousValidator Setup

Last updated