--- Day changed Mon Mar 26 2018
00:02 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me]     
00:43 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning     
01:27 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning     
01:35 -!- ee [d4731682@gateway/web/freenode/ip.212.115.22.130] has joined #c-lightning     
01:35 < ee> hi there
01:36 < ee> ive some question about listpeers command outline
01:36 < ee> is there anyone to willing to help a newbie? :)
01:36 -!- ee is now known as ee888     
01:41 < hkjn0> ee888: try it, you can just ask any questions you have, no need to ask to ask
02:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
02:12 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me]     
02:47 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
02:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning     
03:13 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds]     
03:42 < rompert> i'm going to ask, without asking for permission first: when will this problem with "Adding block 468440" etc get solved? my node lives in the past and never gets up to date before crashing. rusty? someone? please?
03:46 < CubicEarths> rompert: is there an open issue on github?
03:47 < rompert> CubicEarths: i thought there was but i couldn't find it today
03:47 < CubicEarths> just curious, because I have not experienced that issue
03:48 < rompert> apparently it adds from oldest channel and investigates each block after that
03:49 < rompert> closest one i found, which is closed, is this one https://github.com/ElementsProject/lightning/issues/1002 . however i've never run my nodes on testnet.
03:49 < CubicEarths> what block does 'getinfo' reveal?
03:51 < CubicEarths> and what kind of machine are you running your node on?
03:51 < rompert> 468464 now, and last in log is "Adding block 468466"
03:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds]     
03:53 < shinohai> It appears to be advancing, albeit slowly.
03:54 < rompert> i have on two machines. one is a 24 core HP server with 128G ram. the other one is a vps and i tried maximizing that to similar specification but the vps one is much slower. i'll upgrade my HP clightning now and see how fast it really is
03:55 < CubicEarths> Is this issue on the HP server?
03:55 < rompert> yup about 4 blocks per minute 
03:55 < rompert> regarding slowly
03:55 < rompert> HP server i don't use much but i'll upgrade it to check how fast it processes blocks
03:57 < rompert> just need to find that fancy a2x thingy :)
03:57 < CubicEarths> I never trust VPS stuff for security or heavy compute loads :(
03:58 < CubicEarths> I probably should....
03:58 < rompert> or maybe not :) 
04:01 < rompert> for the record, my VPS was much quicker installing a2x than the HP :)
04:02  * CubicEarths looks up a2x, and is confused
04:03 < rompert> it is something needed for latest master. asciidoc something
04:04 < rompert> and that in turn needs like 150 other packages
04:05 < CubicEarths> wow     
04:05 < CubicEarths> I am a few days behind master
04:10 < rompert> lol i should have symlinked a2x to true or something. it will take ages to install everything required for asciidoc
04:17 < rompert> ok here we go on big ass server:
04:17 < rompert> 2018-03-26T11:16:50.654Z lightningd(13765): Adding block 503819
04:23 < rompert> ok that one is much faster, however it doesn't have much other stuff going on and far less channels
04:27 < rompert> it processes like 60 blocks per minute compared to 4, so it will be caught up in like 3 hours
04:28 < rompert> and the main node will take 8 days
04:29 < rompert> (if the miners stop mining new blocks)
04:38 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 264 seconds]     
04:39 < ee888> hi folks
04:40 < ee888> i get an error message like this:
04:40 < ee888> CHANNELD_NORMAL:Received error from peer: channel 161e669bc0e2d56154463356dae31ce3ac8e1aee16c1b39649faf1e02bef82ff: update_fee 25000 outside range 500-10545", "ONCHAIN:Tracking their unilateral close", "ONCHAIN:All outputs resolved: waiting 22 more blocks before forgetting channel" ] } ] }, 
04:40 < ee888> anyone could give me some advise about it please ? :)
04:42 < p3tr> i think that means that the other node didn't agree on some fees regarding updating channel state so it closed it and your node is telling you that it is tracking the TX on the blockchain and waiting X blocks before it forgets about the (already closed) channel
04:44 -!- deusexbeer [~deusexbee@093-092-177-126-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 264 seconds]     
05:12 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning     
05:15 < ee888> ty p3tr
05:16 < ee888> non agreement fees are about funding channel fee's or transaction fee's ?
05:17 < ee888> my fee rates are: "override-fee-rates" : "12015/10500/4000"
05:20 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer]     
05:22 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning     
05:35 -!- Mark__ [5bd4cf04@gateway/web/freenode/ip.91.212.207.4] has quit [Ping timeout: 260 seconds]     
05:41 < ee888> anyone ?
05:44 < p3tr> certainly not funding fee since the channel already was funded - so probably the fee related to commitment (~transaction) or closing fee
06:05 < ee888> ty again p3rt..one (and hopefuly last) more question: then how can i update the value and update the network node ?
06:08 -!- shesek [~shesek@5.102.197.11] has joined #c-lightning     
06:08 -!- shesek [~shesek@5.102.197.11] has quit [Changing host]     
06:08 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
06:22 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds]     
06:23 -!- User__ [~User@133-203.dorm.ncu.edu.tw] has quit [Quit: Leaving]     
06:24 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #c-lightning     
06:50 -!- dougsland [douglas@nat/redhat/x-apsuuyykmgujvhor] has joined #c-lightning     
07:00 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vqoulstqjkxoeqen] has quit [Quit: Connection closed for inactivity]     
07:14 -!- ee888 [d4731682@gateway/web/freenode/ip.212.115.22.130] has quit [Quit: Page closed]     
07:17 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has quit [Ping timeout: 276 seconds]     
07:20 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has joined #c-lightning     
07:40 < hkjn0> rompert: I think https://github.com/ElementsProject/lightning/issues/1179 is the issue you want to follow to reduce the rescanning
07:51 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
08:13 < rompert> hkjn0: ah there it was. perfect. thanks!
08:24 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning     
09:11 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving]     
09:44 -!- nizhanali [ddde8322@gateway/web/freenode/ip.221.222.131.34] has joined #c-lightning     
09:53 < nizhanali> Hi,everyone. I have some problems for run c-lightning .
09:53 < nizhanali> I set up a bitcoin miannet node . When i pay 0.0005btc for my bitcoin address. Command looks like 'docker exec lightning lightning-cli newaddr { "address" : "3GudabJFZZXDsvWbrEWThZZizq8eCbed8R" } ' ，but no result is empty '   docker exec lightning lightning-cli listfunds { "outputs" :    [  ], "channels" :    [  ] } '   :joy: . Who know ?
09:53 < nizhanali> My local blockchain data is update new now
09:53 < nizhanali> docker logs bitcoind_mainnet --tail "10"  2018-03-26 16:03:18 UpdateTip: new best=0000000000000000003f96ed186921817036f9d24c6e532778166682fd8799d3 height=515258 version=0x20000000 log2_work=88.440768 tx=306802827 date='2018-03-26 16:03:02' progress=1.000000 cache=288.3MiB(1804930txo)
09:54 < nizhanali> Thanks！
10:06 -!- donaloconnor [~quassel@80.111.255.30] has joined #c-lightning     
10:18 -!- donaloconnor [~quassel@80.111.255.30] has quit [Ping timeout: 265 seconds]     
10:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
10:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning     
10:56 < nizhanali> Anybody?
11:03 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning     
11:34 -githubby:#c-lightning- [lightning] cdecker opened pull request #1279: wallet: Remove pruned outpoints from utxoset outpoint_filter (master...cleanups) https://git.io/vxENX
11:37 -!- deusexbeer [~deusexbee@176.59.15.27] has joined #c-lightning     
11:40 -!- deusexbeer [~deusexbee@176.59.15.27] has quit [Read error: No route to host]     
11:40 -!- deusexbeer [~deusexbee@176.59.15.27] has joined #c-lightning     
11:45 -!- nizhanali [ddde8322@gateway/web/freenode/ip.221.222.131.34] has quit [Quit: Page closed]     
11:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
11:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning     
11:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 276 seconds]     
12:16 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 240 seconds]     
12:17 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning     
12:33 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-plpkxloxqkcrszzr] has joined #c-lightning     
12:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
12:54 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me]     
13:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]     
13:03 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning     
13:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
13:27 -!- jb551 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning     
13:28 -!- jb551 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Client Quit]     
13:35 -!- shesek [~shesek@2.55.23.235] has joined #c-lightning     
13:35 -!- shesek [~shesek@2.55.23.235] has quit [Changing host]     
13:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
13:36 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me]     
13:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
13:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds]     
13:43 -!- donaloconnor [~quassel@80.111.255.30] has joined #c-lightning     
13:50 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has joined #c-lightning     
13:59 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning     
14:14 -!- suili [2e3bc424@gateway/web/freenode/ip.46.59.196.36] has joined #c-lightning     
14:39 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 240 seconds]     
14:39 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me]     
14:47 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning     
14:48 -!- dougsland [douglas@nat/redhat/x-apsuuyykmgujvhor] has quit [Ping timeout: 246 seconds]     
15:10 -!- donaloconnor [~quassel@80.111.255.30] has quit [Ping timeout: 240 seconds]     
15:11 -!- shesek [~shesek@bzq-84-110-232-249.cablep.bezeqint.net] has joined #c-lightning     
15:11 -!- shesek [~shesek@bzq-84-110-232-249.cablep.bezeqint.net] has quit [Changing host]     
15:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning     
15:33 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me]     
15:50 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning     
15:56 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me]     
16:03 -!- deusexbeer [~deusexbee@176.59.15.27] has quit [Ping timeout: 265 seconds]     
16:05 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]     
16:05 -!- booyah [~bb@193.25.1.157] has joined #c-lightning     
16:07 -!- suili [2e3bc424@gateway/web/freenode/ip.46.59.196.36] has quit [Quit: Page closed]     
16:09 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning     
16:10 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]     
16:10 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has quit [Read error: Connection reset by peer]     
16:10 -!- booyah [~bb@193.25.1.157] has joined #c-lightning     
16:14 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me]     
16:14 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]     
16:15 -!- booyah [~bb@193.25.1.157] has joined #c-lightning     
16:17 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning     
16:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
16:24 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me]     
16:36 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vxuEL
16:36 -githubby:#c-lightning- lightning/master 6269a4c practicalswift: Remove unused functions not covered by unit tests
16:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds]     
16:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
17:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]     
17:41 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning     
17:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
17:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning     
18:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
18:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]     
18:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
18:13 -!- nizhanali_ [ddde8322@gateway/web/freenode/ip.221.222.131.34] has joined #c-lightning     
18:13 < nizhanali_> Hi,everyone
18:14 < nizhanali_> When i start to bitcoind, there is something wrong ,like  ' docker run --name bitcoind_mainnet -d -v /mnt/bitcoinmainnet/bitcoind:/data -p 8333:8333 -p 9735:9735 dougvk/bitcoind:latest docker: Error response from daemon: Conflict. The container name "/bitcoind_mainnet" is already in use by container "19009f21cdb441588b30cf5a30fc6fb6bba7572a14cb02117d7037eb75aa0778". You have to remove (or rename) that container to be able to
18:14 < nizhanali_> Who know ? thanks
18:26 < CubicEarths> This would be a big project, but it seems like it will be (or already is!) important to have a way to 'sync up' two nodes. Like, two identical nodes. Not just for redundancy, but even for planned outages, upgrades, etc  
18:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning     
18:41 -!- cluelessperson [~cluelessp@unaffiliated/cluelessperson] has quit [Quit: Laters]     
19:25 < aj> CubicEarths: you'd have to be very careful about not getting into a split-brain state. maybe just requiring all nodes to confirm channel closure is correct before any node publishes is enough though
19:43 -!- nizhanali_ [ddde8322@gateway/web/freenode/ip.221.222.131.34] has quit [Ping timeout: 260 seconds]     
20:08 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]     
20:44 -!- Saevar [2e166296@gateway/web/freenode/ip.46.22.98.150] has quit [Quit: Page closed]     
20:51 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning     
21:18 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
21:19 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]     
21:19 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning     
21:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 276 seconds]     
21:23 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-plpkxloxqkcrszzr] has quit [Quit: Connection closed for inactivity]     
22:01 -!- weedcoder [~weedcoder@pro75-4-82-238-201-154.fbx.proxad.net] has joined #c-lightning     
22:16 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 268 seconds]     
22:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
22:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning     
22:29 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds]     
22:29 -!- dafunkiz_ [~dafunkizd@172.92.143.143] has joined #c-lightning     
22:49 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds]     
23:14 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 260 seconds]     
23:25 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning     
23:29 -!- dafunkiz_ [~dafunkizd@172.92.143.143] has quit [Quit: probably someone interrupted me]     
23:30 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 265 seconds]     
23:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds]     
23:51 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning