Execution & settlement

The transaction lifecycle

A user reviews and authorizes an exact order. Source payment records the commitment. The destination executor delivers the requested asset or records recovery. A trusted receipt witness checks finalized evidence; the Monad Core then accepts settlement, mints and allocates actual received fees.

Approval is not payment. Payment is not delivery. Delivery is not Monad settlement. A provider success response alone cannot mint a Relation Token.

Configured execution routes

The current deployment supports separate Monad same-chain Uniswap v3 execution and Monad-funded Ethereum Uniswap v3 execution via CCTP. Ethereum output goes to the original Ethereum recipient. Identity, Relation Tokens and economic settlement remain on Monad.

BSC, Base, Arbitrum, Optimism and Polygon have discovery/development adapters. They are not enabled public trading routes in this release.

Finality and duplicate prevention

Canonical finalized source and destination receipts, the exact deployment domain, participants, asset and original recipient are checked separately. The same exchange evidence cannot be accepted again to mint new tokens.

Pending and recovered orders

Closing or reopening the application does not authorize another payment. Unknown submissions are reconciled before retrying. A timeout alone does not prove failure or enable a refund. Recovered orders return funds under their original route rules and produce no Mint.