For Protocols & DApps
How Toby protects your users from harmful MEV and gives your protocol real-time market intelligence.
Your users are getting sandwiched, and most of them don't even know it. Toby gives protocols the tools to protect their users from harmful MEV without adding friction or complexity to the user experience.
The Problem Today
MEV extraction is a silent tax on your protocol's users:
Sandwich attacks hurt execution quality. Every time a user submits a swap on your DEX or protocol, bots can front-run and back-run the trade, extracting value and giving the user a worse price. This happens automatically, invisibly, on nearly every large trade.
Zero visibility. Most protocols have no way to measure how much MEV is being extracted from their users, which validators are running sandwich strategies, or how it impacts overall execution quality.
Limited protection options. The few MEV protection solutions that exist are either user-facing (requiring users to opt in or use special RPC endpoints) or validator-level (requiring protocols to run their own infrastructure). Neither scales well.
Eroding trust. Users who consistently get worse execution than expected will eventually leave. "Why did my swap cost more than the quote?" That question drives users to competitors, or off-chain entirely.
How Toby Fixes It
Toby's OpenMEV infrastructure gives protocols MEV protection at the infrastructure layer. No changes to your UX required.
MEV protection by default. Toby's OpenMEV filters sandwich attacks at the protocol level. Users transacting through integrated protocols get protection automatically, without needing special wallets, RPCs, or settings.
OtterFlow data feed. Real-time market intelligence piped directly to your protocol. Monitor transaction flow, spot anomalies, and understand how MEV interacts with your contracts.
Allow-list hooks. Protocols can define rules for what types of MEV strategies are allowed to interact with their contracts. Want to permit arbitrage (which improves price accuracy) but block sandwiching (which hurts users)? Set it via the OpenMEV Council governance framework.
Better execution quality. With harmful MEV filtered out, your users get the prices they expect. Better execution means happier users, more volume, and stronger retention.
How It Works
Integration is lightweight:
Integrate with Toby's OpenMEV infrastructure. Connect your protocol to Toby's block-building pipeline so transactions flowing through your contracts are MEV-aware.
Set allow-list rules via the OpenMEV Council. Define which MEV strategies can interact with your protocol. Arbitrage? Yes, it corrects prices. Sandwich attacks? Blocked. These rules are community-governed, not imposed top-down.
Users get MEV protection automatically. Once integrated, every transaction on your protocol passes through Toby's filtering layer. No user action needed. Protection is invisible and smooth.
Access OtterFlow for real-time data. Use OtterFlow's market data feed for analytics, monitoring, and building smarter protocol features on top of real-time transaction flow.
Key Benefits
Protect users from sandwich attacks without adding any UX friction. No special wallets, no opt-in flows, no extra clicks.
Better execution quality leads to happier users, more volume, and stronger retention. Users stay where they get the best prices.
Real-time market intelligence via OtterFlow. Monitor how MEV affects your protocol, spot trends, and build data-driven features.
Community-governed rules. The OpenMEV Council ensures that MEV policies are decided collectively, not by a single entity. Your protocol has a voice in shaping the rules.
Position your protocol as MEV-aware. Users are increasingly educated about MEV. Being proactively protective is a competitive advantage.
Get Started
Ready to protect your users?
Getting Started Guide: integration walkthrough for protocols
OtterFlow: real-time data infrastructure and market intelligence
OpenMEV Council: governance framework for MEV policy
Last updated