--- Day changed Mon Mar 12 2018 00:05 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has joined #c-lightning 00:42 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 245 seconds] 02:03 -!- CubicEarths [~cubiceart@c-73-157-2-231.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 02:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:08 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning 02:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 02:13 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has joined #c-lightning 02:31 -!- CubicEarths [~cubiceart@c-73-157-2-231.hsd1.wa.comcast.net] has joined #c-lightning 02:45 -!- CubicEarths [~cubiceart@c-73-157-2-231.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 03:21 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has quit [Ping timeout: 260 seconds] 03:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 04:03 < bitonic-cjp> Is there a way, for testing purposes, to artificially delay the release of the preimage by the payee? What amount can I get away with without hitting time-outs of other nodes? 05:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:33 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 06:08 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 06:27 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #1202: peer_control: Print both `to_self_delay` in listpeers. (master...both-to-self-delay) https://git.io/vxv5u 06:30 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-evruelqogqkahkuz] has quit [Quit: Connection closed for inactivity] 06:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:54 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vxvNC 06:54 -githubby:#c-lightning- lightning/master 1de1242 ZmnSCPxj: peer_control: Print both `to_self_delay` in listpeers. 06:58 -!- douglas_ is now known as dougsland 06:58 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Changing host] 06:58 -!- dougsland [~douglas@tchelinux/moderator/dougsland] has joined #c-lightning 06:58 < mlz> how do you force-close a channel in c-lightning? 07:02 < p3tr> mlz: if close doesnt work try dev-fail 07:02 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 276 seconds] 07:03 < p3tr> for close to work you need to be connected to the other node 07:03 < p3tr> at least i think so 07:03 < mlz> p3tr, ok here's the thing: I have this channel that I tried to close 3 weeks ago but it's still in this state: "state": "CHANNELD_SHUTTING_DOWN", 07:04 < mlz> I did try "dev-fail" 3 weeks ago but it didn't do anything so i'm not sure what to try now 07:04 < mlz> i'll just try to close it again then.. sec 07:06 < mlz> { "code" : -1, "message" : "Peer is in state CHANNELD_SHUTTING_DOWN" } 07:06 < p3tr> and when you try dev-fail again? 07:10 < mlz> p3tr, it gave me a txid but also gave me an error msg 07:10 < mlz> this msg: 2018-03-12T14:07:04.193Z lightning_gossipd(13887): Unable to find channel 510696:820:0 07:10 < mlz> 2018-03-12T14:07:04.222Z lightningd(13879): sendrawtx exit 26, gave error code: -26?error message:?16: bad-txns-vout-empty? 07:11 < mlz> the other node is offline completely 07:11 < p3tr> hm that seems like it cannot correctly submit a closing tx to the blockchain 07:11 < p3tr> can you give me the tx id it told you? 07:12 < mlz> (tx e6486148b001db08a9932a69b1214725bb50e9c2a6687484165c5cf722a8f9a2) 07:12 < p3tr> yeah as i thought - that tx is not on the blockchain 07:13 < p3tr> so it creates the closing tx but bitcoin node rejects it for some reason (it complains about bad outputs it seems?) 07:13 < p3tr> i remember there was some fix related to TX in clightning recently, what version are you running? 07:14 < p3tr> if you are on something older than a week or so i would try updating and doing dev-fail again 07:15 < p3tr> this fix is what i'm talking about, sounds like it could be the cause for that error: https://github.com/ElementsProject/lightning/commit/45e145df5efab5ffe6ced26cb94bd9b57013ec7c 07:16 -!- deusexbeer [~deusexbee@080-250-077-186-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 252 seconds] 07:17 -!- deusexbeer [~deusexbee@093-092-176-255-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 07:18 < mlz> hm im wondering if i closed with a high fee that the channel doesn't have enough to pay 07:18 < mlz> how do you check what fees you're having? 07:20 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 07:20 < mlz> p3tr, im on this version: "version": "v0.5.2-2016-11-21-2264-g3e9e199", 07:21 < p3tr> you can do dev-setfees and not pass any arguments to see the fee settings 07:22 < mlz> ah cool, thanks, this is what i have: { "immediate" : 2418, "normal" : 2102, "slow" : 294 } 07:23 < mlz> ok let me update and try again 07:25 < p3tr> looks like your version is quite recent though updating might help :) 07:26 < p3tr> those are interesting fees though... where did it come up with such weird numbers 07:27 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 07:27 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 07:35 < mlz> p3tr, actually a friend helped me and told me to set those fees :D 07:37 < p3tr> oh 07:39 < p3tr> try bumping the fees up and see if that helps with closing the channel 07:41 < p3tr> its in satoshi per kw, so if it ever used the slow option that could mean a fee of less than 1 sat/byte which i think is not allowed by most nodes 07:50 < mlz> p3tr, hm ok so i just did the update and the fees changed: { "immediate" : 2532, "normal" : 723, "slow" : 294 } 08:11 < mlz> ok just tried with fees { "immediate" : 2454, "normal" : 2454, "slow" : 2454 } but still the same issue 08:17 < p3tr> im out of ideas :( 08:27 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 256 seconds] 08:34 < lxer> "CHANNELD_NORMAL:Funding transaction locked. Waiting for their announcement signatures." <-- what does it mean and what should I do about it? 08:56 -!- renlord [~ry@unaffiliated/renlord] has quit [Quit: out capturing raining bitcoins with a bamboo sieve] 08:56 -!- mryandao [~mryandao@unaffiliated/mryandao] has quit [Quit: do not disturb. look busy...] 09:03 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 245 seconds] 09:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:04 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving] 10:40 -!- CubicEarths [~cubiceart@c-73-157-2-231.hsd1.wa.comcast.net] has joined #c-lightning 10:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 11:36 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:54 -!- Giant_Cube [~corey@c-73-157-2-231.hsd1.wa.comcast.net] has joined #c-lightning 12:09 -!- Giant_Cube [~corey@c-73-157-2-231.hsd1.wa.comcast.net] has quit [Quit: Leaving] 12:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:34 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 12:37 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Remote host closed the connection] 12:38 -!- llou [~textual@cm-83-97-182-195.telecable.es] has joined #c-lightning 12:38 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Client Quit] 12:38 -!- llou [~textual@cm-83-97-182-195.telecable.es] has joined #c-lightning 12:44 -!- llou [~textual@cm-83-97-182-195.telecable.es] has quit [Quit: Textual IRC Client: www.textualapp.com] 12:47 -!- llou [~textual@cm-83-97-182-195.telecable.es] has joined #c-lightning 12:51 -!- CubicEarths [~cubiceart@c-73-157-2-231.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 13:00 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-syspczbohxskpmau] has joined #c-lightning 13:30 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has quit [Ping timeout: 264 seconds] 13:31 -!- lxer [~lx@95.91.214.87] has joined #c-lightning 13:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 13:43 < mlz> "...26 error code: -26?error message:?16: bad-txns-vout-empty?" :( how did it create an empty vout? :/ 13:44 < mlz> i think i'll put this node in storage until someday if i can find answer 13:54 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me] 13:58 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 14:21 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: that's all folks] 14:23 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 14:25 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Client Quit] 14:25 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 14:48 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 14:49 -!- buZz [~buzz@unaffiliated/buzz] has quit [Ping timeout: 260 seconds] 14:49 -!- arowser [~quassel@106.120.101.38] has joined #c-lightning 14:50 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Ping timeout: 260 seconds] 14:50 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning 14:50 -!- buZz [~buzz@unaffiliated/buzz] has joined #c-lightning 14:55 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me] 15:10 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 15:11 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Client Quit] 15:35 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1180: gossip: Use the internal utxoset to verify channels and store capacity in routing table (master...trackblocks2) https://git.io/vAdpX 15:36 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 15:50 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me] 16:13 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 245 seconds] 16:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:26 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 16:29 -!- lxer [~lx@95.91.214.87] has quit [Ping timeout: 264 seconds] 16:33 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has joined #c-lightning 16:46 -!- shinohai [shinohai@ny1.hashbang.sh] has joined #c-lightning 16:56 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 17:09 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 17:20 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 256 seconds] 17:36 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 17:38 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 17:50 -!- dafunkiz_ [~dafunkizd@209.63.143.172] has quit [Quit: probably someone interrupted me] 18:53 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 19:10 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 19:11 -!- dougsland [~douglas@tchelinux/moderator/dougsland] has quit [Ping timeout: 256 seconds] 19:17 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has joined #c-lightning 19:30 -!- jojeyh [~delphi@2602:306:b8b6:b970:fc4e:a12:3352:1c1e] has joined #c-lightning 19:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 19:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 20:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:10 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds] 20:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 20:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:21 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning 20:25 -!- jimbouki [~smuxi@98.227.189.229] has joined #c-lightning 20:26 -!- jimbouki [~smuxi@98.227.189.229] has quit [Remote host closed the connection] 20:34 -!- jimbouki [~jimbouki@98.227.189.229] has joined #c-lightning 20:37 -!- shesek [~shesek@bzq-84-110-235-58.cablep.bezeqint.net] has joined #c-lightning 20:37 -!- shesek [~shesek@bzq-84-110-235-58.cablep.bezeqint.net] has quit [Changing host] 20:37 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 20:43 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:50 -!- jimbouki [~jimbouki@98.227.189.229] has quit [Remote host closed the connection] 21:03 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Ping timeout: 240 seconds] 21:06 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning 21:13 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1206: Gossipd more cleanups (master...gossipd-more-cleanups) https://git.io/vxJgG 21:14 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 240 seconds] 21:19 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 21:26 < CubicEarths> For how long does -connect keep trying to connect before giving up? 21:28 -!- jasan [~jasan@2001:0:d91f:ca12:2cc6:3f17:a099:c530] has quit [Ping timeout: 240 seconds] 21:28 -!- jasan [~jasan@2001:0:d91f:ca12:2cc6:3f17:a099:c530] has joined #c-lightning 21:42 -!- amp__ [~amp@24.136.5.183] has quit [Remote host closed the connection] 21:42 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning 22:02 < MarcioJr> Hello there, I am trying to make it clear about the fees but no luck yet. Since the dev-setfees command is related to on-chain fees (and shouldn't be used in production 'cause it overwrites the dynamic fees, thus is dev- ), what is the command that defines the LN (off-chain) fees ? 22:03 < MarcioJr> Also, what is the best way to check preciselly how much fee was paid on a payment? 22:03 < MarcioJr> Any help will be very appreciated. 22:07 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #c-lightning 22:25 < almkglor> I believe it's an option flag somewhere 22:25 < almkglor> lemme try to dig it up 22:26 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 22:26 < CubicEarths> When I try to fund a channel, I get the 'feerate below minimum' message. I am running on mainnet. 22:26 < almkglor> --fee-base and --fee-per-satoshi for on-LN (off-chain) fees 22:27 < CubicEarths> Are those per-funding tx? 22:27 < almkglor> @CubicEarths, issue #1194 22:28 < almkglor> @CubicEarths, sorry, I was answering @MarcioJr's earlier question about OFF chain fees 22:28 < almkglor> funding transaction is an onchain fee. 22:29 < almkglor> --fee-base and --fee-per-satoshi controlls offchain fees 22:29 < almkglor> @CubicEarths the usual thing is to use dev-set-fees command, haha 22:31 < CubicEarths> almkglor: Without setting that, I am assuming it uses fee estimation? If I set that, does it permanently override the fee estimation? 22:31 < almkglor> @MarcioJr there's no statistics yet, hahaha, they're working on it 22:32 < almkglor> @CubicEarths I think so. There were issues (which are not fixable on c-lightning) where a newly-started bitcoind gives ridiculous fees (too high, too low) for smart(dumb?) estimation 22:33 < almkglor> does that apply to you? (i.e. newly-started bitcoind) 22:34 < CubicEarths> The chain has been fully synced for 5 days now, and I successfully funded channels yesterday. 22:34 < CubicEarths> But today I am getting the "low fee" error 22:34 < almkglor> hmm, well, dunno, go ping the devs on issue #1194 I guess? 22:35 < CubicEarths> I guess so 22:37 < almkglor> looks like they don't (can't?) check minrelaytxfee? 22:37 < almkglor> and estimatedumbfee is being dumb and going below the minrelaytxfee 22:38 < CubicEarths> Would the fix really be as simple as adding a lower bound to the fee estimator such that it never went below minrelay? 22:41 < CubicEarths> almkglor: And another issue I noticed, when trying to connect to a node, it was only trying once ever minute or so, so it kept trying for 10 minutes 22:42 < CubicEarths> More normal behavior seems to try every few seconds 22:42 < almkglor> yeah they added that last week or something 22:42 < almkglor> hmmmmmmm wait maybe I remembered that wrong LOL 22:43 < almkglor> I think I remember an issue about throttling something, but it might not be about connect, hahaha 22:43 < almkglor> sorry, something came up, afk.... 23:00 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 23:02 -!- arowser [~quassel@106.120.101.38] has joined #c-lightning 23:11 -!- r251d [~r251d@2600:1700:e350:37f0:35d2:fc0d:a824:74e5] has joined #c-lightning 23:13 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has quit [Ping timeout: 260 seconds] 23:20 -!- r251d [~r251d@2600:1700:e350:37f0:35d2:fc0d:a824:74e5] has quit [Read error: Connection reset by peer] 23:43 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 246 seconds] 23:45 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 23:59 -!- douglas_ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 248 seconds]