DOCSBook a call
Documentation
On this page ↓
Docs/Integration
MOKUNA DOCUMENTATION

Target networks

Plan network coverage without assuming production availability.

Mokuna’s target scope includes Base, Robinhood, Arbitrum, Optimism, Unichain and Monad. Availability is confirmed with the team for each network and environment.

BasebaseTarget
RobinhoodrobinhoodTarget
ArbitrumarbitrumTarget
OptimismoptimismTarget
UnichainunichainTarget
MonadmonadTarget

What “Target” means

Target identifies the network’s place in Mokuna’s intended scope. It does not mean the network has a public endpoint, an active integration or general production access. The list is not a live status dashboard.

Confirm for each network

  • The precise network and environment your platform needs.
  • Current integration availability and the approved connection method.
  • Submission, ordering and confirmation behavior.
  • Rate limits and your expected traffic profile.
  • Revenue attribution and settlement details.
  • The test plan, operational owner and rollout requirements.

Preview API identifiers

Use base, robinhood, arbitrum, optimism, unichain or monad in the proposed network field. Slugs identify the intended network; they do not establish access or availability.

Operating across multiple networks

Keep configuration and reconciliation separated by network. Do not infer that availability, timing or transaction-handling behavior on one network carries over to another.

Bring your prioritized network list to a technical discussion ↗. Use the same checklist for each proposed integration.

Updated September 20, 2026 · Discuss this guide ↗

Search by topic or keyword. Use ↑ ↓ to choose a result, Enter to open.