Implementation Status

An Intents capability crosses several independently shipped layers. A protocol design or solver implementation is not, by itself, a released developer or wallet feature. Last reviewed against the live deployment on 2026-10-20.

Status Vocabulary

Label	Meaning
Specified	The required messages, contracts, or profile behavior are documented
Implemented	A reference solver or client contains the behavior
End-to-end reference path	The complete reference flow exists, with the caveats listed
Generally available	A released client surface and supported product path are available without manual assembly
Beta	A released reference surface; expect changes and use test funds
Not generally available	No released client surface yet
Client only	The client ships the route, but no supported solver serves it

Capability Matrix

Capability	Terms	Solver implementation	Client implementation	Current availability
Asset exchange	RFQ. If the card names a relay, the solver’s signed quote over Nostr sets the amounts; otherwise the client prices the swap from the card’s feed and `fee_bps`	Reference solver available	Swap client in `@arkade-os/swap`: `quote`, `accept`, `exchange`, `cancel`	End-to-end reference path; mutinynet only (BTC/USDT)
Addressed Lightning send	RFQ (relay)	Implemented in the reference solver	Swap client: `pay` with a BOLT11 invoice	End-to-end reference path; beta on the mainnet preview, within the card’s bounds
Addressed Lightning receive	RFQ (relay)	Implemented in the reference solver, served on the preview deployment	Swap client: `receive({ via: 'lightning' })`, and the client claims	Beta on the mainnet preview; online claim required
Addressed onchain send	RFQ (relay)	Implemented in the reference solver	Swap client: `pay` with a Bitcoin address or BIP21 URI, and the client claims the onchain fill	Beta on mutinynet only
Addressed onchain receive	RFQ (relay)	Not supported: Run a Solver keeps it off, and `intent-solver`’s main branch has removed it	Swap client: `receive({ via: 'onchain' })`	Client only
Published requests	RFQ (relay)	Lightning-send bidding only	General publisher not shipped	Not generally available
Offline Lightning receive	RFQ (relay)	Served by the same solver	`lnurl-server` with `OFFLINE_SELF_CLAIM` quotes and claims while the wallet is offline (Run Lightning Services); the swap client claims only while the app runs	Beta
Registry discovery	Shared discovery	Static registry and reducer available	The swap client reads the network’s registry and pinned cards (`discovery`)	Beta; application curation required
Solver cards over Nostr	Shared discovery	Reference solver publishes its card (kind `38859`)	The discovery client fetches listed solvers’ cards from their relays	Implemented
Nostr RFQ transport	RFQ (relay)	Reference service accepts Nostr	The swap client opens the Nostr transport itself; `nostrRfqTransport` in `@arkade-os/swap/nostr` builds one by hand	Beta

Current Solver Boundary

intent-solver is the open-source reference solver: the matrix above calls it the reference solver and the reference RFQ service. One deployment fills funded asset swaps, answers RFQ over a relay, and serves the Lightning and onchain corridors through LND. Run a Solver sets it up.

Current Client Boundary

The @arkade-os/swap package is published to npm; its source lives in arkade-os/ts-sdk. Integration guides document the actual surface and its known gaps; applications should pin the version they test.

Draft Boundaries

Nostr kinds 24859, 24860, and 38859 remain provisional.
Signed RFQ bids and quotes are attributable but not bonded.
The current RFQ design reuses one key for transport and settlement identity.
Corridor contracts currently carry BTC on both legs.
The key of the operator’s cosigner that emulates Arkade Script is a per-network constant pinned in @arkade-os/sdk, not read from the operator. Each swap client can override it with the optional emulatorPubkey setting (33-byte compressed hex).

When a draft and the reference implementation disagree, implemented behavior takes precedence and the unresolved design remains explicit.

Understand Intents

Build with Intents

Earn Fees

Reference

Status Vocabulary

Capability Matrix

Current Solver Boundary

Current Client Boundary

Draft Boundaries

Primary Sources

​Status Vocabulary

​Capability Matrix

​Current Solver Boundary

​Current Client Boundary

​Draft Boundaries

​Primary Sources

Status Vocabulary

Capability Matrix

Current Solver Boundary

Current Client Boundary

Draft Boundaries

Primary Sources