Jesse de Wit

@yaslama I changed it back to use the same table. I did add a migration to add explicit columns for all opening fee params settings fields. That way it's clear...

Related: https://github.com/BitcoinAndLightningLayerSpecs/lsp/issues/94

> This is lower priority, right? Getting lsps2 to work on CLN should be our main goal. Yes exactly. We'll implement CLN first. Then SDK. Then at some point LND.

Put on hold until https://github.com/lightningnetwork/lnd/pull/7067 is merged.

An idea is to use the min-/max_payment_size_msat fields in the opening fee params to determine the allowed size of a channel.

> I do see a pending PR in greenlight for web hooks > I think the intention in this PR is to notify before force close exactly for this use...

Closing this for now, because greenlight webhooks are suitable for most usecases.

There is this PR for webhook support, but it looks like it's not aimed at specific usecases yet: https://github.com/Blockstream/greenlight/pull/334

Related https://github.com/breez/lspd/pull/181

Put on hold until https://github.com/breez/lspd/pull/166 is merged