OEV RFP Process Update (July 2025)

Thanks to everyone who’s voted and contributed to the discussion so far.

After reviewing all recent comments—including those from @victator and @Gauntlet—and speaking directly with each of the vendors, my position remains largely the same: the DAO should adopt a measured, risk-aware rollout of OEV providers, with clear guardrails and sufficient time to observe real-world performance before expanding further. That being said, I’ve changed my position in a few respects.

My Updated Position:

  • Chainlink on Ethereum Mainnet: I continue to support deploying Chainlink SVR on mainnet—but only for a single market initially. This creates a lower-risk testing environment. All OEV solutions should be evaluated for 1–2 months, ideally through a market stress event, before expanding to other markets. The same standard should apply to RedStone, Api3, and any future OEV deployments.
  • Chainlink on Base: I’ve updated my vote to support deploying Chainlink SVR on Base as well. While I was previously more cautious, I now see Base as a logical next step—contingent on SVR being fully live before year-end. If mainnet performance is solid, Base presents strong growth potential and minimal additional complexity.
  • RedStone on Unichain: No change. I continue to support deploying RedStone on Unichain. If Chainlink is delayed on certain L2s and RedStone demonstrates strong performance, I’d be open to expanding their role—but only after a proper evaluation period that includes volatile conditions.
  • Api3 on Mantle: No change. It’s live and generating revenue for the DAO, and I’m comfortable continuing to monitor its performance within that scope—but any future expansion should be subject to the same evaluation standards as the others.
  • Arbitrum, Optimism: No change. Hold off while OEV solutions are evaluated on other chains. The best fit can be adopted on these chains in the near future by Q1 2026 or even sooner.
  • Scroll, Ronin, Linea: No change. These markets remain too small to justify the integration cost at this time. I recommend holding off on any OEV deployment here.

As @victator and @Gauntlet noted, these systems introduce meaningful complexity into the liquidation path. A controlled, data-driven rollout will give the DAO better visibility into safety, incentives, and long-term fit.

Also worth mentioning: partial liquidations (being built by WOOF) are expected to go live next quarter. This change may further influence how OEV is captured across the protocol and reinforces the need for deliberate deployment strategies.

While I understand the desire among some delegates to resolve OEV selection after over a year of discussion, that alone isn’t a good reason to rush. Instead, let’s empower the newly established Compound Foundation to lead the next phase of evaluation, vendor coordination, and long-term integration—aiming for alignment with a preferred provider over time.

Thanks again to everyone contributing to this process.

2 Likes