Warren Togami

It would work fine either way but it would be cleaner and less error prone if you specify filenames only once per `logX-file` entries? You could put colons in those...

Is `large-channels` enabled on the direct peer as well? I know for a fact invoices larger than 10 million sats can work even as a single part.

10 million sats is 0.1 BTC.

I suspect `pay` cleverness of splitting and shadow routing by default to benefit "privacy" might be getting in the way. Other people bypass `pay` by using the lower level `sendpay`...

Splitting is the behavior of the `pay` plugin. The LN protocol does not require it to be split. It can work as one or many parts just the same. IMO...

https://github.com/elementsproject/glightning PeerSwap uses this fork of glightning as the Golang plugin wrapper. It has a bunch of commits on top of niftynei's May 2020 work. You mean dynamic plugins written...

Oops. I meant I tested it with only v0.10.2 where conf options are passed to plugins only during lightningd startup, not during a dynamic load afterwards. I didn't test 0.11...

> It sounds reasonable, but I am curious what use case is there (other then for plugin development) to need to restart a plugin that registered command line options? *...

The entire reason for this ticket was to ask for lightning config plugins to behave exactly the same as plugins started later. Passing any option a plugin asks for I...

> Would this solve your issue? No, that is terribly inconvenient. If that is all we had in lightningd then I'd opt to instead move all plugin options into its...