Trading
What should I do if a trade fails?
What should I do if a trade fails?
Symptoms: An atomic swap does not complete.Solutions:
- Check your channel liquidity
- Verify the RGB asset details
- Ensure your node is properly synced
- Contact support if issues persist
Can't type the channel capacity I want
Can't type the channel capacity I want
Symptoms: The Channel Capacity field rejects manual input, or only accepts values that start with “50000”.Cause: 50,000 sats is the minimum channel capacity, and the field validates against that floor as you type.Solution: Select the field’s contents and retype the full number in one go, rather than editing digit by digit — for example, select all and type
500000 instead of trying to change the leading digits of an existing value. Any amount is accepted as long as it is 50,000 sats or higher.Wallet
How do I restore my wallet?
How do I restore my wallet?
To restore your wallet:
- Use the backup file you created
- Decrypt the backup file with your password
- Wait for the node to sync
Connectivity
Cannot connect to an LSP
Cannot connect to an LSP
Symptoms: Error messages about LSP connection, or unable to open channels.Solutions:
- Check your internet connection is stable
- Verify the LSP URL — default is
https://api.signet.kaleidoswap.com, under Settings → LSP Configuration - Check firewall/VPN settings; required ports are 9735 (P2P) and 9736 (RPC)
- Visit the LSP’s status page, or switch to a different LSP if available
RGB Lightning Node isn't available locally on Windows
RGB Lightning Node isn't available locally on Windows
Symptoms: No option to run a local node on Windows, or local node setup fails.Cause: The RGB Lightning Node integration is not yet fully supported natively on Windows.Solutions:
- Connect to a remote node instead — self-host on Linux or macOS, or run it in a Docker container and connect to it remotely. See Node Hosting for both options
- Or use a professionally managed option like ThunderStack
- Trading and wallet features work the same way over a remote connection — only local node hosting is affected
My self-hosted node won't start
My self-hosted node won't start
Symptoms: The node exits during startup, or the Desktop App cannot reach its API.Checks:
- Confirm Bitcoin Core is running and that the configured RPC host, port, username, and password are reachable from the node
- Confirm the configured indexer and RGB proxy endpoints are online
- Review the node logs for the first startup error, then restart after correcting the related connection setting
Cannot connect the Desktop App to my remote node
Cannot connect the Desktop App to my remote node
Symptoms: The app reports that the remote node is unreachable or stays disconnected.Checks:
- Verify the node URL in Settings > Node Connection and confirm the node is running and unlocked
- Make sure the server firewall allows the node API port (default:
3001) and Lightning peer traffic on9735 - If you use a VPN, reverse proxy, or tunnel, confirm it forwards traffic to the same address and port configured in the app
My node is stuck synchronizing
My node is stuck synchronizing
Symptoms: The node remains in a syncing state and wallet or channel actions are unavailable.Checks:
- Allow Bitcoin Core to finish synchronizing before retrying
- Check that the configured Electrum or Esplora indexer is caught up with the selected network
- Verify the node, Bitcoin backend, and indexer all use the same network
Mutinynet node or transactions are not working
Mutinynet node or transactions are not working
Symptoms: A Signet node cannot connect, or transactions do not confirm on Mutinynet.Checks:
- Use a Bitcoin build and Electrs configuration that support Mutinynet/Signet
- Confirm the node is configured with
NETWORK=signetand the correct Mutinynet seed nodes - Check the Mutinynet Explorer for network status and transaction confirmation
Get Help
Check the FAQ for questions rather than errors. For anything else, report a problem through your preferred channel from the options below, including:- Your OS and version (macOS, Windows, or Linux)
- KaleidoSwap Desktop App version
- Node type (local or remote) and version
- Steps to reproduce
- Error messages or screenshots
- Log files:
- macOS:
~/Library/Application Support/KaleidoSwap/logs/ - Windows:
%APPDATA%/KaleidoSwap/logs/ - Linux:
~/.config/KaleidoSwap/logs/
- macOS:
Telegram Community
Ask the community.
GitHub Issues
Report a bug on the relevant repository.
Email Support
Direct support for urgent issues.
Download the Desktop App
Get the latest KaleidoSwap Desktop App release for macOS, Windows, or Linux.