Privacy & trust
Understand what the private route changes and where its boundaries are.
Mokuna receives customer transaction flow through a private connection and processes it using its own MEV engine. It does not broadcast that flow to external searchers or run a third-party searcher auction.
The private route
Keeping search and execution within Mokuna removes the external searcher distribution step. This limits that source of exposure to calldata copying and auction circumvention.
This is an architectural property, not a guarantee of absolute secrecy or protection against every MEV behavior. Mokuna must process the transaction, and execution requires a path to the target chain.
On-chain visibility
Included transactions and execution results are visible according to the network’s rules. A private submission path does not make on-chain activity confidential. Your application should explain the difference between private submission and public chain visibility.
Review partner-side routing
A public fallback route or simultaneous submission elsewhere may expose a transaction independently of Mokuna. Review all submission paths, logging systems and third-party services that receive transaction data.
- Map the components that handle signed transactions.
- Agree when fallback is permitted and how users are informed.
- Keep credentials and sensitive operational data out of public logs.
- Confirm data retention, access controls and incident contacts during onboarding.
Technical due diligence
Request the security information your organization needs directly from the team. These docs do not assert an audit certification, a published retention policy or a service-level agreement.
See the security overview for the operating model and the integration checklist for rollout review.