Skip to main content
An Arkade Intent records a user-approved result and constraints. Arkade Intents is the application-level integration standard that connects it to a supported route.
A corridor is a settlement environment such as Arkade, Lightning, or Bitcoin L1. A route connects two corridor-and-asset endpoints, such as arkade:BTC → lightning:BTC. A swap is the base execution primitive that completes the route.
Applications can let users pay, receive, and exchange value. The available outcomes depend on which solver, client, asset, and corridor implementations work together.
No. arkd uses settlement intents (BIP322) to authorize batch swaps and VTXO renewal. Arkade Intents is the application-level market and route standard documented here.
Yes. Every route is quote-first: a quote establishes the terms, funding accepts them, and a solver fills. How a quote reaches the application is an implementation detail of each route, covered on its integrate page.
No. A maker order is firm once taken, and nothing here is. The participants are named directly — user and solver; Participants has the full argument.
A solver supplies pricing, inventory, routing, and risk capacity, and operates the software that executes them. The reference solver serves intra-Arkade routes by watching for funded swaps; serving a corridor route additionally means answering RFQ over a relay and coordinating a settlement profile.
Open discovery allows any solver admitted by application policy to appear in the candidate set. A product may instead use pinned solvers or curated registries. Publishing a request is narrower: one intent reaches every subscribed solver, which may return sealed bids.
No. Cards advertise capabilities, indicative fees, limits, feeds, keys, and transports. An Arkade swap becomes enforceable when the user funds the derived contract. A corridor solver’s signed quote binds its short-lived RFQ terms.
A bid is signed and attributable but does not lock funds or begin settlement. The client selects a bid and closes with an addressed request whose quote carries the executable terms.
No. Applications choose their discovery sources and solver policy. A compatible solver can fill an open Arkade swap. In RFQ, the application selects a solver before making the route’s first enforceable commitment.
No. Advertised fees are only one input. Price freshness, fill probability, routing capacity, cancellation cost, reliability, and application policy also matter. Intents enables competition but does not guarantee best execution.
Limits and fees are configured per directed corridor. A quote has no separate fee field: from_amount is what the user gives, to_amount is what the user receives, and their spread contains the cost (Fees).
An unused RFQ quote or bid expires without a refund because no value moved. An Arkade swap does not exist until its derived contract is funded.
The funded contract or settlement profile determines cancellation, claim, timeout, and refund behavior. A missing status message does not prove failure; the client reconciles contract and destination-network evidence first.
Recovery depends on the contract path. Some paths become unilateral after a timeout; others require operator, signer, Emulator, or counterparty cooperation. The application must explain and persist the selected path before value moves.
No. Protocol, solver, client, and wallet work ship independently. See Implementation Status for the current layer-by-layer view.
Application developers can choose Lightning or Arkade Assets. Solvers can start at Provide Liquidity. Protocol implementers should use the protocol overview and its focused reference pages.