--- Log opened Thu Jul 15 00:00:07 2021
01:57 < nathanael> i am getting `mempool min fee not met, 154 < 1550` on a try to open a channel with acinq
01:57 < nathanael> does that mean they want the minfee to be 1550 or more and my node says it is only 154?
02:20 < nathanael> oh its about the fee for the funding transaction?
04:10 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning
04:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:43 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has quit [Quit: jasan]
07:16 < ksedgwic> nathanael: yes, that sounds like the on-chain fee for the funding tx is not sufficient
07:24 -!- jasan [~j@tunnel625336-pt.tunnel.tserv1.bud1.ipv6.he.net] has joined #c-lightning
08:15 < nathanael> ksedgwic: thanks for getting back - actually i've set the maxmempool variable of my bitcoind too low, it had nothing to do with c-lightning in the first place
08:15 < nathanael> sorry - i am still learning a lot here, but i am the "learning by doing" kind of person...
08:44 -!- jarthur [~jarthur@2603-8080-1540-002d-3440-ee66-189d-dbb7.res6.spectrum.com] has joined #c-lightning
09:28 < jasan> nathanael: -maxmempool is good to set a bigger mempool, though :)
09:46 < nathanael> jasan: yeah haha - that is what i learned today ;)
10:59 < andrewtoth_> I don't think it's a good idea to set -maxmempool to larger than default.
11:00 < andrewtoth_> Since most nodes use default if their mempools all get full they will reject lower paying txs, while your mempool will still accept your 1 sat/byte tx. You will think it was propagated but no other node will have it.
11:17 < nathanael> andrewtoth_: i agree - in my case i've set it lower than default
12:59 -!- niftynei_ [~niftynei@pool-162-84-140-229.nycmny.fios.verizon.net] has joined #c-lightning
13:04 < niftynei_> man i'm not having a good time with names of options for this funderupdate command. the command takes in a set of optional options, updates them, and then prints out the currently set values
13:04 < niftynei_> some of the options are sat values; our convention for JSON *results* in our RPC is that we always print values out as 'msats'
13:05 < niftynei_> fields that are return sat values then are typically named '<name>_msat'; the python plugin handler will auto-parse these fields into Millisatoshi objects for you 
13:06 < niftynei_> here's the issue i'm having: a sane approach would be to have the option names that you pass in to the command line match the returned JSON field names
13:07 < niftynei_> that requires appending '_msat' to param names then, which i dont want to do because they're *actually* satoshi-denominated fields
13:07 < niftynei_> we just default to 'msat' for outputs because that creates a common amount interface 
13:08 < niftynei_> i've sort of settled on having the returned object just be the param name plus the _msat tag... but it doesnt feel good
13:09 < niftynei_> options seem to be: i tag the input params with '_msat' also (it's an untrue descriptor of valid values for the param however'; tag just the returned values with '_msat'; call them '_sat' and update the python parser so that it auto-picks up those fields also
13:10 < niftynei_> but still print the values out as 'XXXmsat'??
13:11 < niftynei_> last option seems the most sane tbh
13:12 < niftynei_> or call the params '_sat' and the return values '_msat'??
14:29 -!- niftynei_ [~niftynei@pool-162-84-140-229.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds]
16:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:56 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning
16:59 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 255 seconds]
20:53 -!- jarthur_ [~jarthur@2603-8080-1540-002d-6c53-2ea3-89b4-023b.res6.spectrum.com] has joined #c-lightning
20:54 -!- jarthur [~jarthur@2603-8080-1540-002d-3440-ee66-189d-dbb7.res6.spectrum.com] has quit [Ping timeout: 245 seconds]
23:05 -!- jarthur_ [~jarthur@2603-8080-1540-002d-6c53-2ea3-89b4-023b.res6.spectrum.com] has quit [Ping timeout: 255 seconds]
23:06 -!- Guest76 [~Guest76@2603-7000-e102-49c5-95d5-a6db-ebe9-5184.res6.spectrum.com] has joined #c-lightning
23:07 -!- Guest76 [~Guest76@2603-7000-e102-49c5-95d5-a6db-ebe9-5184.res6.spectrum.com] has quit [Client Quit]
23:32 -!- jarthur [~jarthur@2603-8080-1540-002d-b887-749f-7796-49c4.res6.spectrum.com] has joined #c-lightning
23:47 -!- belcher_ is now known as belcher
--- Log closed Fri Jul 16 00:00:07 2021