--- Day changed Tue Aug 14 2018 00:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 01:03 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-cebzizyqtwmchipt] has joined #c-lightning 01:34 -!- ken2812221_ is now known as ken2812221 04:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 04:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 05:10 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 08:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:02 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:05 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 09:12 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 09:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:32 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 10:40 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 10:41 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 10:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:49 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 10:52 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 12:22 -!- jonasschnelli_ is now known as jonasschnelli 13:52 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 14:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 15:21 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 15:31 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 15:41 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:53 < jb55> now ACTIVE was ACTIVE <- I see this a lot in the logs, why would nodes be sending this if they're already active? 15:53 < jb55> unless I've missed a previous channel_disabled message? 15:53 < jb55> but it happens so much... 16:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:54 -!- polydin [~delphi@2602:306:b8b6:b970:3da2:8778:ad8c:877a] has joined #c-lightning 17:06 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 17:18 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:25 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 17:32 -!- polydin [~delphi@2602:306:b8b6:b970:3da2:8778:ad8c:877a] has quit [Quit: Leaving] 18:21 -!- justan0theruser is now known as justanotheruser 18:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 18:50 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:50 -!- justan0theruser is now known as justanotheruser 20:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds] 20:18 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 20:40 < molz> rusty, hi, how can i check if I fund a channel now, what tx fee the tx will pay?? 20:41 < rusty> molz: good q! It's a three-step process, I'm afraid. (1) File an issue. (2) wait for me to code it. (3) get the info you need? 20:41 < rusty> molz: We have our internal fee estimate, we just don't expose it. As it happens, I'm working on that code right now though.... 20:41 < molz> oh ok :) 20:42 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 20:50 < molz> i thought i could find this in 'listconfigs' 21:36 < rusty> molz: it changes, depending on what bitcoind is saying. I've just implemented a command which will give you the current feerates we'll use, but might be nice if getinfo gave an estimate of how much it would *actually* cost to fund a channel. 21:41 < molz> rusty, oh.. cool, that will really help.. 21:43 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 23:36 < rusty> molz: how's this? new `feerates` call: 'sipa': {'urgent': 15285, 'normal': 6250, 'slow': 4916, 'min_acceptable': 300, 'max_acceptable': 300000}, 'onchain_estimates': {'opening_channel_satoshis': 4387500, 'mutual_close_satoshis': 4206250, 'unilteral_close_satoshis': 9140430} 23:38 < rusty> except without the 'unilteral' typo ;) 23:40 < molz> lol 23:40 < molz> rusty, can we set our own fees? 23:40 < molz> it seems "dev-set-fees" is gone? 23:41 < rusty> molz: kind of, you can *influence* them, using the new `feerates` call to inject them manually. Overriding fees has gotten people in trouble before :( 23:41 < rusty> (if you spam it with 10 feerates calls, you'll overwhelm the average and probably get close!) 23:52 < rusty> molz: https://github.com/ElementsProject/lightning/pull/1846 23:55 < molz> wow... 23:56 < molz> oh noes... --dev-override-fee-rates will be removed? I just used it on testnet, works nicely :D