Oval Node
Inner workings of the Oval Node.
The Oval Node is designed to simplify the onboarding process of Oval for searchers. Searchers can simply add a new RPC to their list of builders they send bundles to and the Oval Node takes care of all the special logic required to backrun Oval unlocks.
The Oval Node supports two main RPC methods for searchers:
eth_sendBundle
, to which searchers can send standard bundle constructions as they would to any other builder.eth_callBundle
to which searchers can send standard simulation payloads.
Both of these endpoints behave from the searchers perspective like any other builder they might send bundles to. Note that the Oval Node is not a builder; conceptually it is like a modified version of an MEV-Share node and acts as a middle layer between a searcher and MEV-Share.
Bundle transformation
The Oval Node receives a bundle on the eth_sendBundle
RPC structured as follows:
The Oval Node does three things to this bundle:
It transforms the method from using
eth_sendBundle
tomev_sendBundle
. Equally, it transforms the params block to use themev_sendBundle
definition.It appends the
unlockLatestValue
transaction hash to the incoming bundle and forwards this to the MEV-Share node viamev_sendBundle
method.
The transformed bundle that is forwarded to MEV-Share looks as follows:
The kickback address used by the Oval Node is set at the beginning to a multisig controlled by UMA (see Revenue Sharing). The OEV captured in the kickback will be manually distributed to associated projects that integrate with Oval. In the future this can be updated to operate as a contract to automatically distribute OEV revenue.
Last updated