Settlement Profiles

A settlement profile defines how one directed route becomes enforceable. It specifies required quote fields, who commits first, how timeouts are ordered, which evidence proves completion, and how each side recovers. Adding a route requires a profile, solver implementation, client implementation, and discovery support. A registry entry alone does not make a route usable.

​

Implemented BTC Profiles

Direction changes who funds, who claims first, and which timeout must be longer. Do not implement a reverse route by swapping labels in the forward flow.

​

Arkade to Lightning

The invoice amount is quote.to_amount. The Arkade lockup carries quote.from_amount; the spread is the solver fee. Funding the verified lockup accepts the quote.

​

Lightning to Arkade

The client creates the payment preimage and sends only its hash. The solver creates an incoming hold invoice and funds the Arkade output. Paying the hold invoice is the first enforceable commitment. The client completes the swap by claiming the Arkade output and revealing the preimage. The current reference service waits for the client to claim — the wallet stays online for that step (Implementation Status).

​

Bitcoin L1 Profiles

Bitcoin L1 routes use paired onchain and Arkade HTLCs; the table above gives each direction’s funders. Both client surfaces remain in progress. Use the table here as protocol reference, not as evidence of released wallet support.

​

Fees

Corridor pricing can contain:

• a basis-point spread that scales with the amount; and
• a flat satoshi component for corridor costs that do not scale with value.

The quote carries no separate fee field. The difference between from_amount and to_amount represents the complete cost under the selected profile.

​

Asset Boundary

The current reference corridor contract commits to a destination and minimum output value but does not yet commit to an asset identity. The implemented corridor profiles therefore carry BTC on both legs. Arkade-to-Arkade exchanges use a different non-interactive swap contract that does bind asset identity. See Arkade Asset Swaps.

​

Reference Timing Bounds

These values describe the current reference profiles, not universal defaults for future corridors.

​

Recovery Rule

A relay timeout or missing status response does not prove failure. Reconcile the funded contract and destination-network evidence before reporting a result or attempting recovery.