payments

Background

If my node is asked to forward N sats to peer X via channel C, lnd is free to pick any other channel it might have to peer X. As far as I understand the code (switch.go:handlePacketForward), all channels to X (not just C) are checked for eligability, and a random eligable channel is then used for the actual forward.

As part of this eligability check (implemented in link.go:Che

Should be a nullable ForeignKey on Subscription.

https://stripe.com/docs/api/subscriptions/object#subscription_object-latest_invoice

Tentatively add to 2.2 milestone since it seems like it should be simple (potentially would hit a cyclic sync issue though, due to Invoice.subscription relation).

I have two setups using bitcoind v21.99.0.

Eclair testnet (SQLite backend) has started without wallet parameter in config while mainnet (Postgre) didn't and I could only make it working with provided wallet.

I had to restart mainnet bitcoind because I was thinking that it was in failed state but apparently wallet was loaded and I reloaded it again after restart. Everything returned back