Skip to main content
The Swap SDK speaks the Boltz /v2 protocol and keeps compatibility with upstream Boltz through an explicit base URL. The KaleidoSwap maker serves a subset of the Boltz public API and adds routes of its own. An exported SDK method does not by itself mean a given maker serves the route it needs. The API Reference lists every route the KaleidoSwap maker serves. swapAuth and its recovery, atomic swaps, pay-through, and the Arkade corridor are KaleidoSwap additions that upstream Boltz does not serve.

​
Not served by the KaleidoSwap maker

These upstream Boltz capabilities stay in the Rust core so you can use them against a compatible maker. They are not exported to the TypeScript, Python, or React Native bindings, and the KaleidoSwap public maker does not register their routes. To broadcast, use your own chain backend: BtcLikeTransaction.broadcast in TypeScript, ChainClient.broadcast_tx natively. WASM’s constructCooperativeClaim is a chain-swap claim constructor. It does not expose submarine co-signing.

​
Pointing the SDK at another maker

Pass the maker’s base URL explicitly (see Networks). Then:
  • Read its pair catalogues at runtime instead of assuming routes.
  • Expect swapAuth to be absent on an upstream Boltz maker. Methods that take it accept undefined for a maker that issues none.
  • The SDK’s create-time checks reject a response that differs from the protocol: an inexact timeout height, a non-minimal timelock encoding, or a lockup that does not match your keys. A maker that diverges from Boltz there will fail those checks by design.