Skip to main content

​
Channel Operations

The channel group covers direct Lightning channel management against your local node. Peer arguments use pubkey@host:port format. Closing needs both the channel ID and --peer; add --force for a unilateral close, and only when the peer is unresponsive, since it locks funds until the timelock expires.

​
Open A Channel

Notable options:
  • --capacity
  • --push-msat
  • --asset-id
  • --asset-amount
  • --push-asset-amount
  • --public or --private
  • --with-anchors
  • --fee-base-msat
  • --fee-proportional-millionths
Example colored channel:

​
LSP Channel Orders

Use channel order when you want KaleidoSwap’s LSP flow instead of manually opening a peer channel.

​
Subcommands

​
Create an order

The pubkey is optional and defaults to your local node, so kaleido channel order create --lsp-balance 1000000 --client-balance 500000 is equivalent when you are ordering for yourself. Useful options:
  • --confirmations, default 6
  • --funding-within, default 144 blocks
  • --expiry-blocks, at least 1
  • --refund-address, defaulting to a local node address
  • --announce or --private
  • --asset-id
  • --lsp-asset-amount, required with --asset-id
  • --client-asset-amount, which must not exceed --lsp-asset-amount
  • --email
  • --yes, -y to accept the fetched RFQ price, required non-interactively

​
Pay an order

Choose the funding source with --onchain or --offchain; interactively the CLI asks, but in --agent or --json mode exactly one is required, along with --yes. On-chain payments accept --fee-rate in sat/vbyte. Example colored channel order:

​
LSP Metadata

The lsp subgroup exposes server metadata and network details: These commands are useful before creating orders or when wiring client defaults.

​
Practical Sequence

See Market And Swaps for server-side trading flows that often run alongside channels and liquidity management, or Troubleshooting when a channel or an order will not go through.