4 Commits

Author	SHA1	Message	Date
Rusty Russell	cb5dc48cab	lightningd: make setchannelfee handle multiple channels per peer. ... Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2022-03-23 13:20:12 +10:30
Rusty Russell	5704653d4c	setchannel: don't let them advertize htlc_maximum_msat larger than capacity. ... And check for the obvious setting min > max. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2022-03-22 18:45:41 +10:30
Rusty Russell	999c734bb5	setchannel: add minhtlc ... Suggested by @m-schmook, I realized that if we append it later I'll never get it right: I expect parameters min and max, not max and min! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Protocol: you can now alter the `htlc_minimum_msat` and `htlc_maximum_msat` your node advertizes.	2022-03-22 18:45:41 +10:30
Rusty Russell	66e264d6b3	lightningd: new setchannel command. ... Based on setchannelfee, but expanded to allow setting max htlc amount (and others in future?). The main differences: 1. It doesn't change values which are not specified (that would be hard to add fields to!) 2. It says exactly what all values are in any potentially changed channels. Changelog-Added: JSON-RPC: new `setchannel` command generalizes `setchannelfee`. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2022-03-22 18:45:41 +10:30