Skip to main content
Arkade Intents is a request-for-quote system on every route: a user states an intent, a quote establishes the terms, the user funds, and a solver fills. The market structure never varies by route. Only the settlement contract does: To build against these routes, start from Swap Client.

The Quote

A quote commits the terms a swap executes on. A quote fixes the amounts, the settlement key, the timeouts, and the window in which funding may start. It does not guarantee completion. Once value is committed, the settlement contract decides the valid claim and recovery outcomes, not the quote. The first commitment accepts the quote: there is no separate accept message.

Who Commits First

The direction of the route decides which side commits value first: Corridor Swaps covers each direction in full: the paired contracts, the timeout order, and the recovery path.

Fill or Refund

After funding there are exactly two outcomes: the solver fills, or the commitment comes back. Cancel and refund are the same step, reached by different scripts. A cross-corridor route refunds through a timelocked path in the HTLC, so a deadline delivers it. A route with both sides settling through Arkade cancels by submitting the cancel transaction to Arkade, with no solver signature, so recovery never waits on the solver. That swap has no fill deadline, but its deposit keeps its batch expiry: a deposit still unfilled at that expiry is swept, and stays recoverable.

Participants

A user approves the desired result and, through a wallet or application, funds it. A solver supplies pricing, inventory, and risk capacity, and fills the funded contract. Some specifications use provider or market maker as synonyms for solver.

Discovery and Open Markets

A request for terms is addressed to one solver, encrypted to its key, or published so every solver watching the pair may answer with a sealed bid the application selects from locally. Which solvers are candidates at all is application policy (pinned cards, curated registries, or open discovery), and Discovery and Registries covers those sources. Publishing reaches bidders; it does not obligate a product to expose every solver. In the developer preview only the addressed form is in use: applications pin one solver, and nothing publishes a request yet.

Arkade Intents Protocol

Discovery, RFQ, settlement profiles, states, and invariants.

Trust and Limitations

What each component guarantees, and what it does not.