-
Notifications
You must be signed in to change notification settings - Fork 974
Description
I observed some strange behavior on my lightning node (version 0.10.0)
Issue and Steps to Reproduce
Two days ago I changed my fee rates to achieve the goal of setting a zero base fee with lightning-cli setchannelfee all 0 21 I also changed the values in my config file in case I later restart lightning.
Today I was examining how many nodes in gossip are signaling zero base fee and I realized that my node didn't do so despite having done so two days ago.
By checking listpeers I observed that my node was having the old fee policy that I had from before.
However after running lightning-cli setchannelfee all 0 21 again the output of listpeers also shows the new policies as expected.
I don't have the time right now to check the code or log file I wonder if the config values are kept in memory and are not being updated so that the node will eventually reset all the fees after using lightning-cli setchannelfee all 0 21.
I will not restart my node now but rather observe if the fees will be reset again. if so I will restart and see what happens.
getinfo output
lightning-cli getinfo
{
"id": "03efccf2c383d7bf340da9a3f02e2c23104a0e4fe8ac1a880c8e2dc92fbdacd9df",
"alias": "ln.rene-pickhardt.de",
"color": "03efcc",
"num_pending_channels": 0,
"num_inactive_channels": 0,
"address": [
{
"type": "ipv4",
"address": "144.76.235.20",
"port": 9735
}
],
"binding": [
{
"type": "ipv4",
"address": "144.76.235.20",
"port": 9735
}
],
"version": "v0.10.0",
"blockheight": 691110,
"network": "bitcoin",