API3’s key product claim is simple: return oracle-linked MEV to the dApp instead of letting the full opportunity leak to searchers and validators.
When a price-feed update makes a liquidation or arbitrage profitable, searchers normally race for transaction order. API3’s OEV model instead auctions exclusive rights to execute that update, allowing the winner to update the feed and perform the action atomically.
According to API3’s documentation, 80% of the resulting OEV revenue goes to the partner dApp as OEV Rewards; the remainder is retained as a protocol fee. Rewards are paid in the native gas token of the dApp’s chain—not necessarily in $API3 , and not automatically to every API3 holder.
Why it matters: an oracle integration can become a revenue line for a DeFi protocol, not only a cost. The adoption signal to watch is recurring OEV rewards from live integrations, not a short-term candle.
Sources: docs.api3.org/dapps and /oev
#API3 #DeFi
When a price-feed update makes a liquidation or arbitrage profitable, searchers normally race for transaction order. API3’s OEV model instead auctions exclusive rights to execute that update, allowing the winner to update the feed and perform the action atomically.
According to API3’s documentation, 80% of the resulting OEV revenue goes to the partner dApp as OEV Rewards; the remainder is retained as a protocol fee. Rewards are paid in the native gas token of the dApp’s chain—not necessarily in $API3 , and not automatically to every API3 holder.
Why it matters: an oracle integration can become a revenue line for a DeFi protocol, not only a cost. The adoption signal to watch is recurring OEV rewards from live integrations, not a short-term candle.
Sources: docs.api3.org/dapps and /oev
#API3 #DeFi
