Architecture
One privately connected engine, from opportunity search to execution.
Mokuna’s core design keeps MEV search and execution with one operating team. Partners supply transaction flow; Mokuna runs the engine that identifies opportunities and prepares them for execution.
The transaction route
- Partner → Mokuna
The partner routes transaction flow through a private connection configured with the team.
- Search
Mokuna’s proprietary engine looks for on-chain arbitrage opportunities associated with that flow.
- Simulate
The engine evaluates opportunities before execution. A simulation is an assessment against a particular state, not a guarantee about the eventual block.
- Execute
Mokuna packages transactions for on-chain execution. The exact submission path depends on the network and agreed integration.
- Share captured value
Captured MEV revenue is shared with the integration partner according to the agreed accounting and settlement terms.
Where responsibilities sit
| Area | Partner | Mokuna |
|---|---|---|
| Order flow | Own the application’s routing and user experience. | Receive flow through the agreed private connection. |
| MEV processing | Coordinate integration requirements. | Run search, simulation and execution strategies. |
| Transaction tracking | Reconcile submission records with on-chain outcomes. | Agree on available submission and execution signals. |
| Economics | Agree attribution and reconcile statements. | Share captured MEV revenue under agreed terms. |
No external searcher auction
Mokuna does not broadcast customer transactions to a third-party searcher network or ask external searchers to bid on them. Its own engine performs the search and execution. That is the architectural distinction to retain when evaluating other order flow products.
The number of external searchers is only one part of the privacy picture. Transactions still need to be submitted for on-chain execution, and included transactions become observable on the chain.
Network-specific details
Submission paths, ordering, finality and failure handling depend on the target network. Do not assume Ethereum RPC behavior, builder relationships or a competitor’s API contract applies to a Mokuna integration. Confirm these details per network using the API reference.