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 repository state on August 12, 2026.

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

Capability Matrix

Capability	Terms	Solver implementation	Client implementation	Current availability
Arkade Asset exchange	RFQ; quote computed client-side today	Reference solver available	Published `@arkade-os/swap` package	End-to-end reference path; beta/test funds
Addressed Lightning send	RFQ (relay)	Implemented in reference RFQ service	Request helper, manager, and Nostr transport in `@arkade-os/swap`	End-to-end reference path; beta/test funds
Addressed Lightning receive	RFQ (relay)	Implemented in reference RFQ service	Request builder and claim helper (`requestLightningReceive`, `claimReceiveLockup`); no manager entry	End-to-end reference path; online claim required
Addressed Bitcoin L1 send	RFQ (relay)	Implemented in reference RFQ service	TypeScript feature work	Not generally available
Addressed Bitcoin L1 receive	RFQ (relay)	Implemented in reference RFQ service	No generally released client	Not generally available
Published requests	RFQ (relay)	Lightning-send bidding only; flat-fee bids skipped	General publisher not shipped	Not generally available
Receive claim automation	RFQ (relay)	Adapter present but intentionally unwired	Client must claim	Not generally available
Registry discovery	Shared discovery	Static registry and reducer available	Discovery packages available or in feature work by market type	Beta; application curation required
Nostr RFQ transport	RFQ (relay)	Reference service accepts Nostr	`nostrRfqTransport` ships in `@arkade-os/swap/nostr`; adopted by the reference wallet	Beta

Current Solver Boundary

Two reference services cover different routes:

solverd watches for funded Arkade Asset swaps and fills compatible markets.
The reference RFQ service serves corridor routes; it is closed source while its HTLC state machine is audited.

Do not treat one as a drop-in implementation of the other.

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 Emulator key is resolved by the client package from the Arkade operator; an optional emulatorPubkey override (33-byte compressed hex) remains available per call.

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

Primary Sources

Reference Arkade solver
RFQ Protocol — the reference RFQ service is not yet public
Solver Registry
@arkade-os/swap package

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