Pay from any chain, cash out to any chain

A farmer’s premium does not have to start as USDC on NEAR, and a payout does not have to stay there. NEAR Intents routes either direction through its solver network, so the market contract only ever sees NEP-141 USDC and nobody has to acquire NEAR for gas to buy cover.

Why this is mainnet and dry. NEAR Intents has no testnet and none is planned — the organisers’ own guidance is mainnet with tiny amounts and dry: true quotes. So the market contract runs on testnet and this panel talks to the real mainnet 1Click API in dry mode. A dry quote is a real quote: real routing, real fees, a real ed25519 signature over the terms. It commits nothing and moves nothing.

Quotes are dry: true — real routing, real fees, a real signed quote, and nothing moves. NEAR Intents has no testnet, so this is the only way to exercise the integration without spending mainnet funds.

Where the money sits, at every step

All seven statuses 1Click can report. A dry quote never enters this lifecycle; a live one does, and the two that matter most are the two that are easy to swallow: REFUNDED and FAILED.

StatusMeansWhere your funds are
PENDING_DEPOSITWaiting for your depositStill in your wallet on the origin chain. Nothing has moved.
KNOWN_DEPOSIT_TXDeposit seenYour deposit transaction is visible on the origin chain, not yet confirmed.
PROCESSINGSwappingHeld by the Intents solvers mid-route. Neither chain shows it as yours yet.
SUCCESSDoneUSDC has arrived at the recipient on NEAR. The premium can be paid.
INCOMPLETE_DEPOSITDeposit too smallLess arrived than the quote required. It sits at the deposit address until you top it up or it is refunded.
REFUNDEDRefundedSent back to your refund address on the origin chain, minus the refund fee the quote showed.
FAILEDFailedThe route could not complete. Funds are refunded to the refund address; nothing is left with us.
The recipient has to be a mainnet account. The market contract lives on testnet, but NEAR Intents settles mainnet USDC — there is no testnet to settle on. Passing a .testnet recipient makes 1Click reject the quote with a bare 400 Internal server errorand no explanation, so it is worth saying plainly. In a production deployment the market and the Intents recipient would be the same mainnet account; here they cannot be.

How this fits the rest of Mmiri

  1. A buyer holds USDC on Base, Arbitrum, Solana — wherever they already are. They ask 1Click for a quote into USDC on NEAR with the market as recipient.
  2. They send the origin funds to the deposit address the live quote returns. The solvers route it and USDC lands on NEAR.
  3. That USDC opens a round through the contract’s NEP-141 ft_on_transfer hook, carrying the terms in the message — the same path an underwriter uses to deposit capital.
  4. When a policy pays, the holder receives NEP-141 USDC. The same panel in reverse quotes taking it out to whichever chain they want to spend it on.
What is not built. The live path — submitting a deposit and polling /v0/status through to SUCCESS — is implemented behind ONECLICK_LIVE, which is off here, and has not been exercised with real funds. The status table above is the full set of states the code handles, not a record of states we have observed. We would rather say that than show a screenshot of a swap that never happened.
Asset ids are read live from /v0/tokens (230 tokens at last check) rather than hardcoded — a stale id is a swap into nothing. Amounts are integer strings in each token’s base units. A JWT is not required for quotes; it only changes the fee tier, and this deployment has none.