Gm Kyle,
just to go into this point.
Platonia has done retrospective analysis on API3’s OEV solution for Compound on Mantle. They will be releasing the results of this in the next few weeks.
Currently Compound doesn’t utilize the correct proxies on Mantle that allow for optimal OEV recapture. Compound currently utilizes the “global feed” (mentioned by WOOF! above) meaning, there is no way to bid to update & pay Compound exclusively.
At the time of integration a revamped version of the dApp specific proxies was undergoing audit, which is why the Compound integration on Mantle was performed with the global feeds only. Additionally, the OEV matter on Compound wasn’t approved or cleared which is why we didn’t want to force that in without approval from the DAO either.
It is true however, that we’ve paid Compound well over $150K already on the deployment, because our parnter searchers also have the ability to update the global feed with the 30 second delay, which allowed them to recapture every single liquidation that occured in Feb.
So whatever analysis is currently being done by Platonia on the Compound Mantle Deployment isn’t really reflective of a “correct”/true OEV integration utilizing API3. For that Compound would need to utilize Compound specific proxies, which we would only supply after the DAO approves the usage of an OEV solution.