pull down to refresh

FlashSats mostly follows the proposed LSP standard: https://github.com/BitcoinAndLightningLayerSpecs/lsp/tree/main/LSPS1
The LSP standard would allow buyers to compare rates charged by different LSP providers. This channel/info API would give buyers a basic understanding of the offering. The values are static.
There are three channel sizes here
  1. lsp_balance: initial sats on my side.
  2. client_balance: initial sats on your side.
  3. channel_balance: (lsp_balance + client_balance).
The max_client_balance_sats is set to zero because I do not want to push sats to the other end for security reasons. I doubt I will ever change that. You can ignore 3
Instead of pushing sats to the client side, I am open to implementing the dual-fund-channel feature where customers will provide PSBT for the dual-fund-channel.