Integration checklist
A working checklist for engineering, product and operations.
Use this checklist to define acceptance criteria with the Mokuna team. Use the Preview API to evaluate the proposed contract, then confirm the implementation and operating limits before rollout.
Access and network scope
- Confirm each network, environment and current availability.
- Obtain the approved connection address and authentication instructions.
- Record request size, throughput and rate limits, if applicable.
- Identify technical owners on both sides and an escalation channel.
Routing and transaction handling
- Map where the transaction is signed and which components receive it.
- Review parallel submissions and public fallback behavior.
- Agree nonce ownership and the source of pending-transaction information.
- Specify timeout, retry and duplicate-submission handling.
- Confirm whether replacement and cancellation are supported and how they work.
Validation scenarios
| Scenario | Acceptance question |
|---|---|
| Valid submission | What response is expected, and how is the final chain outcome verified? |
| Malformed or unauthorized request | How is the error surfaced without exposing credentials? |
| Timeout or connection loss | How is an uncertain submission reconciled before retrying? |
| Duplicate submission | Can the application safely identify repeated requests? |
| Pending or replaced transaction | Which signal is authoritative for the application’s next action? |
| No profitable opportunity | How are transaction execution and revenue reported separately? |
| Route unavailable | What triggers rollback, and what privacy tradeoff does fallback introduce? |
Revenue and reporting
- Agree the captured-revenue calculation basis and applicable costs.
- Confirm partner attribution and the format of reconciliation records.
- Agree settlement asset, network, destination, schedule and minimums, if any.
- Define how discrepancies are investigated and resolved.
Rollout and operations
- Set the initial scope and criteria for expanding traffic.
- Monitor submission outcomes, pending age, chain inclusion and reconciliation.
- Document rollback ownership and the trigger conditions.
- Verify that user-facing messaging does not promise guaranteed inclusion or revenue.
Bring the completed checklist to a technical review ↗ before production rollout.
Updated September 20, 2026 · Discuss this guide ↗