I've found a few issues related to LSPS1-spec compliance.
Pick lower default value for funding_confirms_within_blocks
By default the LSP-client sets funding_confirms_within_blocks to 288.
However, the spec only allows values up to and inclusive of 255 blocks.
See https://github.com/BitcoinAndLightningLayerSpecs/lsp/issues/112 for more context.
Use bolt11_invoice instead of lightning_invoice.
The spec isn't very consistent and uses bolt11_invoice and lightning_invoice.
However, lightning_invoice is only used in some examples.
I expect the spec will use bolt11_invoice only.
See https://github.com/BitcoinAndLightningLayerSpecs/lsp/pull/109
Use required_channel_confirmations-field
This field is not set by the client
I've found a few issues related to LSPS1-spec compliance.
funding_confirms_within_blocksBy default the LSP-client setsfunding_confirms_within_blocksto 288. However, the spec only allows values up to and inclusive of 255 blocks. See https://github.com/BitcoinAndLightningLayerSpecs/lsp/issues/112 for more context.bolt11_invoiceinstead oflightning_invoice. The spec isn't very consistent and usesbolt11_invoiceandlightning_invoice. However,lightning_invoiceis only used in some examples. I expect the spec will usebolt11_invoiceonly. See https://github.com/BitcoinAndLightningLayerSpecs/lsp/pull/109required_channel_confirmations-field This field is not set by the client