Skip to main content

​
Frequently Asked Questions

No. Your app derives and keeps every swap key. The SDK verifies each swap the maker proposes against your keys before you fund it, and builds claims and refunds on your side. If the maker disappears mid-swap, the script-path refund after the timeout needs only your key.
When a KaleidoSwap mainnet maker is live, forNetwork("mainnet") will resolve to it in a minor release with a changelog entry. Until then the SDK does not silently fall back to a third-party maker.
The Swap SDK adds swaps to a wallet or app and needs no Lightning node of your own. The Node SDK (kaleido-sdk) controls an RGB Lightning Node you run: wallets, channels, RGB assets, payments, and node-to-node swaps.
For submarine and reverse swaps, yes: someone has to receive or pay the Lightning leg, on the same network as the maker. On signet that means Mutinynet, a custom signet: use a Mutinynet wallet or the Mutinynet faucet, which can pay an invoice for you. Chain swaps and atomic RGB swaps need only on-chain wallets.
Yes. Pass any Boltz-/v2-compatible base URL explicitly. Check which routes that maker serves; see Compatibility.

​
Get Help