--- Day changed Sat Jan 27 2018 00:22 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #lightning-dev 01:00 -!- Ingoma [69e93108@gateway/web/freenode/ip.105.233.49.8] has joined #lightning-dev 01:02 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 264 seconds] 01:04 -!- kexkey [~kexkey@173.209.61.61] has quit [Ping timeout: 268 seconds] 01:12 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Snoozing.] 01:15 -!- nirved [~nirved@2a02:8071:b58a:3c00:b8b3:341a:4520:4d1c] has joined #lightning-dev 01:24 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [] 01:28 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 01:35 -!- mughat [~textual@x1-6-28-c6-8e-30-bf-4a.cpe.webspeed.dk] has joined #lightning-dev 01:40 -!- lxer [~lx@ip5f5bd57e.dynamic.kabel-deutschland.de] has joined #lightning-dev 01:41 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lightning-dev 01:51 -!- Sheol_ [4f5b5dbb@gateway/web/freenode/ip.79.91.93.187] has joined #lightning-dev 01:53 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds] 02:14 -!- ralphthe1inja [~lms@c-6469e555.03-130-6e6b701.cust.bredbandsbolaget.se] has joined #lightning-dev 02:14 -!- ralphthe1inja is now known as ralphtheninja2 02:24 -!- Sheol_ [4f5b5dbb@gateway/web/freenode/ip.79.91.93.187] has quit [Quit: Page closed] 02:32 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 02:34 -!- moctost_ [~moctost@209.95.50.117] has joined #lightning-dev 02:36 -!- moctost [~moctost@173.244.200.120] has quit [Ping timeout: 256 seconds] 02:36 -!- moctost_ is now known as moctost 02:37 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Ping timeout: 265 seconds] 02:38 -!- moctost [~moctost@209.95.50.117] has quit [Client Quit] 02:38 -!- moctost [~moctost@209.95.50.117] has joined #lightning-dev 02:40 -!- MaxSan [~user@185.156.175.59] has joined #lightning-dev 02:41 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 02:53 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Remote host closed the connection] 02:53 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 03:08 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Ping timeout: 260 seconds] 03:23 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 03:23 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 03:36 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 03:41 -!- anome [~anome@unaffiliated/anome] has quit [] 03:45 -!- kunla [~kunla@bl4-53-189.dsl.telepac.pt] has joined #lightning-dev 03:47 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 03:52 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has joined #lightning-dev 03:54 -!- anome [~anome@unaffiliated/anome] has quit [] 03:54 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 04:06 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Ping timeout: 256 seconds] 04:11 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 04:11 -!- Ytxyyuu [~Ytxyyuu@78-71-46-150-no260.tbcn.telia.com] has joined #lightning-dev 04:11 -!- tinova33 [~tinova@lemoncat.org] has joined #lightning-dev 04:12 < tinova33> howdy! trying lightningd :D, trying to connect to the blockstream channel (02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432@104.198.32.198) 04:12 < tinova33> getting this error though 04:12 < tinova33> "id 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432@104.198.32.198 not valid" 04:13 < tinova33> any hints where i should look at? Thanks! 04:17 -!- MaxSan [~user@185.156.175.59] has quit [Ping timeout: 240 seconds] 04:23 -!- Pavle [~pavle_@unaffiliated/pavle/x-4679000] has joined #lightning-dev 04:28 -!- Pavle [~pavle_@unaffiliated/pavle/x-4679000] has quit [Ping timeout: 260 seconds] 04:34 -!- JackH [~laptop@i25091.upc-i.chello.nl] has joined #lightning-dev 04:35 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection] 04:35 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 04:40 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 04:42 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #lightning-dev 04:52 -!- Ytxyyuu [~Ytxyyuu@78-71-46-150-no260.tbcn.telia.com] has left #lightning-dev ["Leaving"] 05:01 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has joined #lightning-dev 05:02 < kbasali> Hi 05:02 < kbasali> I have question about how to rename the channel 05:03 < kbasali> Cant find how to give name to my Node 05:04 -!- jfcastro [~jfcastro@176.251.240.17] has joined #lightning-dev 05:09 -!- kunla [~kunla@bl4-53-189.dsl.telepac.pt] has quit [Quit: Leaving] 05:12 < jfcastro> hi all! I'm trying fund a channel with c-lightning and I get message "to_self_delay 600 larger than 432" 05:13 < jfcastro> what means that message? 05:13 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Ping timeout: 256 seconds] 05:17 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lightning-dev 05:19 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 05:23 < kbasali> I think we are all alone here 05:24 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 268 seconds] 05:26 < kbasali> +Roasbeef can you help? 05:26 < kbasali> +roasbeef hii 05:29 < jfcastro> kbasali: do you have a node in ln on testnet? 05:29 < jfcastro> kbasali: if so, could you let me know id, ip and port to connect? 05:30 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #lightning-dev 05:31 < kbasali> no not in test net 05:31 < jfcastro> kbasali: in mainnet? 05:31 < jfcastro> kbasali: with c-lightning? 05:35 < kbasali> yes mainnet 05:35 -!- anome [~anome@unaffiliated/anome] has quit [] 05:37 < kbasali> I'm try to give name my channel but cannot do it yet 05:41 < jfcastro> wow! well done! with lnd or c-lightning software? 05:42 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 05:46 < kbasali> https://blockchain.info/address/34rGLtcSKjYXTrCveE5Rip59LE9FbG8Gaz 05:46 < kbasali> now I do have such a problem :) 05:48 < kbasali> with c-lightning 05:52 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 05:52 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 05:53 -!- eck [~eck@fsf/member/eck] has joined #lightning-dev 05:54 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has joined #lightning-dev 05:54 -!- eck [~eck@fsf/member/eck] has quit [Client Quit] 05:56 < kbasali> lightning-cli fundchannel 023c5f2b69161742cc49da5be6cb7c940465fc608ff216bafc7573eb31121b22d2 10000 05:56 < kbasali> I get this error message 05:57 < kbasali> { "id" : "023c5f2b69161742cc49da5be6cb7c940465fc608ff216bafc7573eb31121b22d2", "connected" : true, "netaddr" : [ "85.148.41.19:9735" ], "channels" : [ { "state" : "CHANNELD_AWAITING_LOCKIN", "owner" : "lightning_channeld", "funding_txid" : "2ed2fe839d5e725b39804662f8fa91525513fa9130cfffa46647747707844983", "msatoshi_to_us" : 10000000, "msatoshi_tot 05:57 < kbasali> any suggestion? 05:57 -!- eck [~eck@fsf/member/eck] has joined #lightning-dev 06:03 < jfcastro> kbasali: it's not an error, i think 06:03 < jfcastro> kbasali: type lightning-cli listpeers 06:04 < jfcastro> kbasali: better: "lightning-cli listpeers 023c5f2b69161742cc49da5be6cb7c940465fc608ff216bafc7573eb31121b22d2 06:05 < jfcastro> kbasali: look your transaction at https://blockchain.info/tx/2ed2fe839d5e725b39804662f8fa91525513fa9130cfffa46647747707844983 06:05 < jfcastro> it's need to be confirmed ;) 06:06 < jfcastro> *needed 06:12 < kbasali> let me try it 06:12 < kbasali> but still I can not create new channel :( 06:15 -!- justus_ [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 06:18 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 06:23 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #lightning-dev 06:23 < kbasali> https://blockchain.info/address/34rGLtcSKjYXTrCveE5Rip59LE9FbG8Gaz Who is going to confirm it? 06:24 < kbasali> Also "Unable to decode output address" having a such a problem :) 06:24 < kousakahonoka> The miners, of course. 06:27 < kbasali> transaction gives such a error "Unable to decode output address" 06:28 < kousakahonoka> You can use another blockchain explorer. Basically it's because OP_RETURN or P2WPKH format. 06:29 -!- daouzo23 [~daouzo23@91.141.1.127.wireless.dyn.drei.com] has quit [Ping timeout: 268 seconds] 06:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-sdpmqewsbgtqrfcr] has quit [Quit: Connection closed for inactivity] 06:31 < kbasali> thank you, 06:31 < kbasali> Do you know how I can change channel name? 06:32 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has joined #lightning-dev 06:32 < kousakahonoka> I'm not familiar with c-lightning commands, but I guess you can find it out with "lightning-cli --help" and there should be some nickname setting options. 06:35 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 256 seconds] 06:35 -!- anome [~anome@unaffiliated/anome] has quit [] 06:37 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 06:43 < kbasali> I'm not fimiliar linux at all :) 06:44 < kbasali> I try help and this is the results 06:44 < kbasali> { "help" : [ { "command" : "dev-blockheight", "description" : "Show current block height" }, { "command" : "dev-setfees", "description" : "Set feerate in satoshi-per-kw for {immediate}, {normal} and {slow} (each optional) and show the value of those three feerates" }, { "command" : "listnodes", "description" : "Show all nodes in our local network view" }, 06:51 < kbasali> its really getting harder for me, Can it be becouse of transactions error? 06:53 < kousakahonoka> No. In lnd there is a clear command for you to set channel nick but I didn't find that in c-lightning documentation...-_-# 06:53 < mlz> gosh...if you're familiar with linux and don't know that you need to wait for a tx to be confirmed because it's the freakin bitcoin, you have no business to be on mainnet 06:58 < kbasali> Thank you fr your advise, Just try to learn it. 06:59 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #lightning-dev 06:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 256 seconds] 07:06 < kbasali> also transactions has a another problemi nothing about wait more. 07:07 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has quit [Quit: WeeChat 2.0.1] 07:07 -!- kunla [~kunla@bl13-61-148.dsl.telepac.pt] has joined #lightning-dev 07:09 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has quit [Quit: Page closed] 07:10 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has joined #lightning-dev 07:11 < mlz> if you're NOT familiar with linux* is what i should've said :P 07:11 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 07:11 < mlz> kbasali, forget mainnet, get on testnet, you won't learn anything by jumping in mainnet just to have a node, it's such vanity like a pink bow on a pig :P 07:12 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lightning-dev 07:12 -!- wxss [~user@185.151.58.115] has joined #lightning-dev 07:13 < eck> linux is too complicated 07:13 < eck> just use amiga 07:13 < eck> very easy 07:16 < kbasali> you are right actually 07:17 < kbasali> Calculater is better 07:19 -!- riclas [~riclas@148.63.37.111] has joined #lightning-dev 07:20 -!- kbasali [b0e94d33@gateway/web/freenode/ip.176.233.77.51] has quit [Quit: Page closed] 07:21 -!- Deelight [~Deelight@75.68.86.79.rev.sfr.net] has joined #lightning-dev 07:26 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 07:26 -!- grubles [~grubles@unaffiliated/grubles] has joined #lightning-dev 07:34 -!- jfcastro [~jfcastro@176.251.240.17] has quit [Quit: Leaving] 07:40 -!- kunla [~kunla@bl13-61-148.dsl.telepac.pt] has quit [Quit: WeeChat 2.0.1] 07:40 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has joined #lightning-dev 07:45 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 07:48 -!- justus_ [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 07:50 -!- cloaks [~noty@unaffiliated/cloaks] has joined #lightning-dev 07:50 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 07:51 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has quit [Quit: WeeChat 2.0.1] 07:52 -!- kunla [~kunla@81.193.53.189] has joined #lightning-dev 07:57 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection] 07:58 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 08:03 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 260 seconds] 08:06 -!- Alex_ [~Alex@79.125.251.64] has joined #lightning-dev 08:08 -!- alexann [~Alex@77.29.147.121] has quit [Ping timeout: 240 seconds] 08:14 -!- Cogito_Ergo_Sum [~Myself@ppp-94-64-157-186.home.otenet.gr] has joined #lightning-dev 08:14 -!- Cogito_Ergo_Sum [~Myself@ppp-94-64-157-186.home.otenet.gr] has quit [Changing host] 08:14 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #lightning-dev 08:21 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has joined #lightning-dev 08:26 -!- cubancorona_ [49ca9483@gateway/web/freenode/ip.73.202.148.131] has quit [Quit: Page closed] 08:43 -!- miller [9d322cd4@gateway/web/freenode/ip.157.50.44.212] has joined #lightning-dev 08:43 < miller> "max_htlc_value_in_flight_msat" : 18446744073709551615, what does that mean 08:44 < miller> how do I change "channel_reserve_satoshis" "htlc_minimum_msat" in c-lightning 08:45 -!- anome [~anome@unaffiliated/anome] has quit [] 08:49 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 08:49 -!- daouzo23 [~daouzo23@178.165.128.161.wireless.dyn.drei.com] has joined #lightning-dev 08:51 -!- cypher [~cypher@unaffiliated/cypher] has quit [Ping timeout: 256 seconds] 08:54 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 08:55 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 08:59 -!- mughat [~textual@x1-6-28-c6-8e-30-bf-4a.cpe.webspeed.dk] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 09:03 -!- cypher [~cypher@unaffiliated/cypher] has joined #lightning-dev 09:07 -!- eihli [~eihli@c-73-241-104-119.hsd1.ca.comcast.net] has joined #lightning-dev 09:15 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 09:19 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds] 09:25 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 09:25 -!- dom_eclair [~dom_eclai@80.12.27.180] has quit [Ping timeout: 240 seconds] 09:27 -!- dom_eclair [~dom_eclai@92.184.96.24] has joined #lightning-dev 09:29 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 265 seconds] 09:30 -!- dom_eclair_ [~dom_eclai@92.184.96.240] has joined #lightning-dev 09:33 -!- dom_eclair [~dom_eclai@92.184.96.24] has quit [Ping timeout: 264 seconds] 09:52 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 09:57 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 248 seconds] 10:00 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 255 seconds] 10:01 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lightning-dev 10:02 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lightning-dev 10:06 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 10:13 -!- miller [9d322cd4@gateway/web/freenode/ip.157.50.44.212] has quit [Ping timeout: 260 seconds] 10:13 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds] 10:14 < lxer> I have this message in c-lightning log, what does this mean? state: FUNDING_SPEND_SEEN -> ONCHAIND_OUR_UNILATERAL 10:15 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 10:15 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 10:18 -!- mughat [~textual@x1-6-28-c6-8e-30-bf-4a.cpe.webspeed.dk] has joined #lightning-dev 10:21 -!- neary [~nate@unaffiliated/neary] has joined #lightning-dev 10:23 -!- emzy [~quassel@unaffiliated/emzy] has joined #lightning-dev 10:25 -!- anome [~anome@unaffiliated/anome] has quit [] 10:27 -!- daouzo23 [~daouzo23@178.165.128.161.wireless.dyn.drei.com] has quit [Ping timeout: 268 seconds] 10:30 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 10:31 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lightning-dev 10:33 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #lightning-dev 10:34 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 10:34 -!- daouzo23 [~daouzo23@178.165.128.161.wireless.dyn.drei.com] has joined #lightning-dev 10:36 -!- daouzo23 [~daouzo23@178.165.128.161.wireless.dyn.drei.com] has quit [Read error: Connection reset by peer] 10:37 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 10:38 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 256 seconds] 10:51 -!- zipadee [2f2ae8cc@gateway/web/freenode/ip.47.42.232.204] has joined #lightning-dev 10:51 -!- zipadee [2f2ae8cc@gateway/web/freenode/ip.47.42.232.204] has quit [Client Quit] 10:57 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has quit [Ping timeout: 240 seconds] 11:01 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lowmfcybswyklflg] has joined #lightning-dev 11:12 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 11:15 -!- grafcaps [325a53e5@gateway/web/freenode/ip.50.90.83.229] has joined #lightning-dev 11:16 < grafcaps> what's the difference between `created_at` and `timestamp` for `listpayments` in c-lightning? I only have 14 payments, but for all of them `created_at` == `timestamp` 11:17 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 11:19 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 11:20 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 11:21 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 11:24 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has joined #lightning-dev 11:26 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Remote host closed the connection] 11:27 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 11:28 -!- anome [~anome@unaffiliated/anome] has joined #lightning-dev 11:28 -!- mk_ [4ded9404@gateway/web/freenode/ip.77.237.148.4] has joined #lightning-dev 11:29 -!- mk_ [4ded9404@gateway/web/freenode/ip.77.237.148.4] has quit [Client Quit] 11:29 -!- princjeblon [4d6ff420@gateway/web/freenode/ip.77.111.244.32] has joined #lightning-dev 11:31 -!- anome [~anome@unaffiliated/anome] has quit [Client Quit] 11:31 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 11:31 -!- princjeblon_ [4d6ff420@gateway/web/freenode/ip.77.111.244.32] has joined #lightning-dev 11:31 < princjeblon_> Hi all. Please can you explain me what mean $ lightning-cli listpeers ... { "state" : "CHANNELD_AWAITING_LOCKIN" ... ? Thanks! 11:31 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has joined #lightning-dev 11:34 -!- princjeblon [4d6ff420@gateway/web/freenode/ip.77.111.244.32] has quit [Ping timeout: 260 seconds] 11:36 -!- princjeblon_ [4d6ff420@gateway/web/freenode/ip.77.111.244.32] has quit [Ping timeout: 260 seconds] 11:37 -!- princjeblon [~princjebl@148.4.wms.cz] has joined #lightning-dev 11:38 < princjeblon> Hi all. Please can you explain me what mean $ lightning-cli listpeers ... { "state" : "CHANNELD_AWAITING_LOCKIN" ... ? Thanks! 11:38 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has joined #lightning-dev 11:44 -!- Adrao [~blabla@155.red-81-44-123.dynamicip.rima-tde.net] has quit [Remote host closed the connection] 11:50 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has joined #lightning-dev 11:53 -!- tonu [~tonu@bd97-1ef7-4e45-f5ec-2980-8b98-07d0-2001.dyn.estpak.ee] has joined #lightning-dev 11:54 < leishman> princejeblon: Did you broadcast the channel funding transaction? 11:57 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has quit [Quit: Mutter: www.mutterirc.com] 11:57 -!- eihli [~eihli@c-73-241-104-119.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 12:02 < princjeblon> lightning-cli fundchannel 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 200000 if you mean this, yes 12:02 < princjeblon> leishman: https://blockchain.info/tx/cf55c17a5cb3848aef388b5d5273776ea891c8a28d7b8e0933fc29dc8c59a57f 12:03 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 12:05 -!- mgxm [~mgxm@unaffiliated/mgxm] has joined #lightning-dev 12:09 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has joined #lightning-dev 12:11 -!- fizzwont [~irc3@unaffiliated/fizzwont] has joined #lightning-dev 12:13 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has quit [Client Quit] 12:13 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lightning-dev 12:20 < lndbot> princjeblon: When you run listpeers, do you see that same tx as the channel funding tx for the peer in the CHANNELD_AWAITING_LOCKIN state? 12:23 < princjeblon> lndbot: if you mean this: "funding_txid" : "cf55c17a5cb3848aef388b5d5273776ea891c8a28d7b8e0933fc29dc8c59a57f"; yes, its same as txid in blockchain: https://blockchain.info/tx/cf55c17a5cb3848aef388b5d5273776ea891c8a28d7b8e0933fc29dc8c59a57f 12:24 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has joined #lightning-dev 12:26 < leishman> princjeblon: is your Bitcoin node up to date with the most recent block? 12:27 < princjeblon> leishman: looks yes, but i try restart it, thx 12:33 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has quit [Quit: Mutter: www.mutterirc.com] 12:34 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 12:34 < princjeblon> in ~ # bitcoin-cli getinfo ... ; "blocks": 506405, ; looks actually 12:34 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined #lightning-dev 12:35 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 12:35 < princjeblon> https://zerobin.net/?b9bad0e832189847#bNgg3hw5jJJJAny7sTG+tpa9HGq6SOsgyGDQC7xjy1A= (lightning-cli listeers) 12:35 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #lightning-dev 12:36 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 256 seconds] 12:39 -!- newbold [~adam@cpe-74-139-234-152.kya.res.rr.com] has joined #lightning-dev 12:39 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lightning-dev 12:40 < newbold> princjeblon, fizzwont is havign the same problem as you 12:40 < newbold> channel funding tx has plenty of confs, but channels stuck in CHANNELD_AWAITING_LOCKIN 12:41 < princjeblon> i dont know if i doing something bad, or only must wait to (...), i try too kill all and start again, but state is same, bitcoind synced ok 12:42 < newbold> https://twitter.com/Cryptolopolis/status/957271684431695878 12:42 < newbold> not a lot of info out there... seems like it may just be a matter of being patient? not really sure :( 12:42 < fizzwont> appreciate your help. any way to "kill" it? it won't let me "close" in that state 12:43 < princjeblon> hmm, really crazy - i try wait and inform you when its there any change. thx 12:43 < newbold> I'd suggest being extra careful on mainnet 12:43 < princjeblon> i have on this server only this, i reboot whole machine :D 12:43 < newbold> I closed a channel manually and my funds didn't make it back to me :P 12:43 < fizzwont> not a huge deal for sure, ready to lose the sats, just trying to clear up my peer list :) 12:44 < princjeblon> sometime i see in debug this: https://zerobin.net/?9e11a638ed03bcec#IxRDnCQjwYrhWRtvg4/MYJH9qoAI0Q6fi+bGMAFftfk= 12:45 < princjeblon> but i dont know if this have any dependence on this problem or not 12:46 < fizzwont> is your stuck channel the blockstream store? 12:46 < newbold> I see that too, I think it's fairly standard lighting "traffic" stuff 12:46 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has joined #lightning-dev 12:47 < newbold> hmm, that's a good question -- if you're both having the same problem with the same peer node, that might suggest an issue with that other node 12:47 < newbold> 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 is sleepyark I think (the blockstream store node) 12:47 < fizzwont> 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 12:47 < fizzwont> thats my stuck one 12:47 < princjeblon> yes its sleepyark 12:47 < newbold> heh 12:47 < fizzwont> ahh 12:48 < princjeblon> its problem?:D 12:48 < newbold> maybe someone at Blockstream needs to restart sleepyark, or check its bitcoin node 12:48 < fizzwont> ^^ 12:48 < newbold> let me see if anyone is around from there on Slack 12:48 < princjeblon> jj 12:50 < newbold> oh those same two guys are already in here, lol 12:51 < newbold> well, I think patiently waiting it out is the best move at this point 12:52 < princjeblon> great, try wait when it change, i write there... thx 12:53 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has joined #lightning-dev 12:53 < fizzwont> thx for your help 12:54 < leishman> Does anyone have a specific explanation as to why this happens? I’m curious. 12:54 < leishman> It’s happened to me a few times as well 12:54 < newbold> yeah, not sure... I still have so much to learn about the protocol at a foundational level 12:54 < newbold> but my guess is that both peers have to agree on a channel state 12:55 < newbold> so if either side is out of whack for any reason (btc node fell behind, etc.) then that agreement simply won't happen 12:55 < fizzwont> maybe the node should auto-drop the channel if the other side doesn't agree after X confirms? 12:55 < newbold> that's just a guess though 12:55 < fizzwont> because i can't get rid of it now 12:55 < newbold> fizzwont: heh my failed peer is still showing up days later, in a funky ONCHAIND_OUR_UNILAT state 12:55 -!- tonu [~tonu@bd97-1ef7-4e45-f5ec-2980-8b98-07d0-2001.dyn.estpak.ee] has quit [Remote host closed the connection] 12:55 < fizzwont> newbold: :/ 12:56 < gwillen> I would encourage people with stuck channels to leave their nodes up 12:56 < leishman> Yeah. So we sent to a 2 of 2 multisig address. That tx confirmed. Now perhaps we’re waiting for them to send their side of the pre-signed refund tx 12:56 < gwillen> until the devs show up 12:56 < gwillen> that will probably make it easier for them to debug 12:56 < newbold> rather ONCHAIND_OUR_UNILATERAL 12:56 < fizzwont> thanks gwillen will do 12:56 -!- napalm` [~client@185.56.20.132] has joined #lightning-dev 12:57 < gwillen> it's sunday morning in australia right now, so rusty might show up or he might be out having a weekend and show up tomorrow :-) 12:57 < leishman> My guess is some sort of node reputation system may start to develop 12:57 < gwillen> well, so far every node is running one of a tiny number of implementations, so it's probably just a bug that someone needs to fix 12:57 < leishman> Yep. 12:57 < newbold> Just found this: https://github.com/ElementsProject/lightning/issues/709 12:58 < gwillen> ahh, if the fix just went in two days ago, that might explain it 12:59 < newbold> when was the last time you pulled the latest code and compiled? 12:59 < leishman> Does anyone have an idea about how mobile or laptop nodes will work with regards to routing since they don’t have static IPs? 12:59 < newbold> yeagh 12:59 < newbold> might not hurt to stop the node, git pull, make, and see if that helps 12:59 < fizzwont> i'm not runing pruned 12:59 < fizzwont> and i grabbed the code a few hrs ago 13:00 < newbold> well, probably can rule that out then :P 13:00 < grubles> anyone running lnd having issues? 13:01 < newbold> grubles: good question since that would further point to an issue with SLEEPYARK if people were 13:01 < newbold> I should set up an lnd instance on another machine, if I can... wish I had the other day, it would be helpful now :P 13:01 < grubles> yeah i'm having an issue 13:01 < gwillen> if sleepyark is blockstream, it will be running c-lightning 13:01 < grubles> disconnect/reconnects 13:01 < grubles> https://github.com/ElementsProject/lightning/issues/814 <- 13:01 < fizzwont> just seems strange that if the other side of a channel is having trouble, our side needs to be able to gracefully get out of it. 13:02 < fizzwont> another blockstream store issue, fun 13:03 < princjeblon> i mean there is not possible do anything on our side... only try other (better?) node 13:03 < fizzwont> yes, other channels are fine. but going forward there should be some protection for this type of incident 13:03 < fizzwont> i just opened a new one, went to NORMAL pretty fast 13:04 < newbold> seems super likely to be a Blockstream channel issue then 13:04 < fizzwont> yes 13:04 < princjeblon> btw for activation of channel need send any transaction, or there is any minimum? 13:05 < newbold> princjeblon: I think there are minimums but they're tiny. There are maximums too... not sure what the values are though 13:05 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 13:05 < fizzwont> but if it's blockstream or rogue_adversary or any other node, being able to "lock" the sender by being bugged or out of sync is not good. i should be able to close it but i can't 13:05 < newbold> fizzwont: yep. This is why despite all of the hype and excitement and mainnet activity, the words of the devs keep ringing clearly in my ears: this is not ready yet :P 13:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lightning-dev 13:06 < mlz> fizzwont, you just opened another channel with Blockstream store and it went to NORMAL? 13:06 < fizzwont> agree, just trying to help - i don't mind losing the sats at all 13:06 < newbold> I think he meant a different node entirely 13:06 < fizzwont> mlz: no, a channel with a different node 13:06 < fizzwont> and it's fine 13:06 < mlz> fizzwont, and you're running c-lightning? 13:06 < fizzwont> yes 13:07 < mlz> fizzwont, and the node you opened a channel with is also running c-lightning? 13:07 < newbold> I'd try to open a channel with SLEEPYARK now but I'm afraid to do anything with my node after https://github.com/ElementsProject/lightning/issues/793 13:07 < fizzwont> i don't know if it's c-lightning, i just picked it off the map to test 13:07 < princjeblon> and i have same problem with SLEEPYARK too 13:07 < mlz> i'm wondering if there's still a lot incompatibility between impls 13:08 < newbold> could be that too 13:09 < fizzwont> someone else should try a new channel to SLEEPYARK, that would seal it :) 13:09 < newbold> got another confirmation from a guy on Slack that his channel to SLEEPYARK is stuck in the same way 13:09 < newbold> 10 confs 13:10 < princjeblon> can i stop channel and start again without new transaction? 13:10 < emzy> I opend a chanel 10 confs ago. still CHANNELD_AWAITING_LOCKIN 13:10 < fizzwont> ^^that's the one 13:10 < princjeblon> emzy: yes same 13:10 < fizzwont> maybe blockstream is testing how they can lock up people's channels.... 13:10 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has joined #lightning-dev 13:10 < emzy> So it's not our end. 13:10 * newbold dons his conspiracy hat :P 13:10 < napalm`> is opening a channel with sleepyark the best way to start? I was just looking at starting mine up also and trying to pick a hub 13:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lowmfcybswyklflg] has quit [Quit: Connection closed for inactivity] 13:11 < fizzwont> not at the moment 13:11 < newbold> napalm`: _normally_ it would be, but it seems that SLEEPYARK is... snoozing? 13:11 < fizzwont> ^ 13:11 < emzy> napalm`: a channel to #reckless worked fine for me. 13:11 < newbold> you could open a channel with any other well-connected node and do a getroute, but even then that might not work if SLEEPYARK is having troubles 13:12 < newbold> emzy: #reckless was the channel I opened the other day that resulted in lost funds when I closed it, heh 13:12 < fizzwont> ouch 13:12 < newbold> we're all having interestingly different experiences and it all just underscores how dangerous and unpredictable it is right now 13:12 < newbold> fun to learn and test though 13:13 < newbold> just treat it like a lottery scratch-off :P 13:13 < napalm`> exactly :) I'm not trying to do anything serious, just run a node on mainnet 13:13 < emzy> ok. Paying do SLEEPYARK via #reckless also do not work. 13:13 < mlz> you can open a channel with my node if you want: "LND is DA BOMB" 13:13 < fizzwont> haha 13:14 -!- leishman [~Mutter@96-64-246-133-static.hfc.comcastbusiness.net] has quit [Quit: Mutter: www.mutterirc.com] 13:14 < gwillen> I encourage people who are having trouble paying sleepyark to keep whatever logs you have, in case they're useful for debugging what happened to it 13:14 < mlz> shameless shilling for LND hahaha 13:14 < newbold> COINGAMING seems to have a connection to SLEEPYARK 13:14 < napalm`> mlz: :D 13:14 < mlz> :D 13:15 < newbold> https://lnmainnet.gaben.win is cool but I'd love to see a directory that provides sortable stats on connectivity 13:15 < mlz> i'm telling noobs not to get on mainnet but if i can't stop them, what can i do 13:15 < napalm`> so after I open a connection it has to be funded to become a channel? I'm still a little lost on the basics 13:15 < newbold> maybe even using standard ONA measures like betweenness/brokerage and such 13:15 < newbold> napalm`: correct 13:15 < fizzwont> is there a better/more updated mainnet map than https://lnmainnet.gaben.win/ ? 13:16 < newbold> napalm`: two prerequisite steps: funding your lightning wallet, and then funding a channel 13:16 < newbold> fizzwont: I haven't seen one 13:16 < mlz> newbold, going to create another rexplorer? :D 13:16 < fizzwont> ok, thx, my node not there :/ 13:16 < newbold> mlz: if I knew how, I would! 13:16 < newbold> oh it's open source 13:16 < newbold> hmm 13:18 < emzy> newbold: which implementation was it you clodes the channel with #reckless? 13:18 < newbold> c-lightning 13:18 < newbold> it went into some kind of CLOSING state (forget the specific name) and then ended with the ONCHAIND_OUR_UNILATERAL 13:18 < newbold> it created the tx to return the funds to me, but my c-lightning isn't recognizing it 13:18 < newbold> so the funds aren't truly lost... just kind of disconnected :P 13:18 < emzy> me,too. So maybe don't close it :) 13:19 < newbold> yes, that's the lesson I learned: don't close channels :P 13:19 < emzy> ok. so you have the key to the funds.. so no problem to recover. 13:20 < newbold> someone is asking for a way to dump the key: https://github.com/ElementsProject/lightning/issues/807 13:21 < fizzwont> yes, i was thinking about getting the privkey and going that way - good question 13:21 < emzy> good to know. 13:26 < mlz> i had bitcoind and c-lightning on ubuntu.. sent coins from bitcoin core wallet to clightning wallet but they never showed up.. not sure maybe my ubuntu had so many things installed so i reinstalled ubuntu and now im installing bitcoind and clightning again to test, and ofc all this all testnet 13:27 < newbold> good to hear it's testnet :) 13:27 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #lightning-dev 13:27 < mlz> oh and a weird thing happened was after i restarted bitcoind and clightning, i got a core dump 13:28 < newbold> I can't seem to find a way to make c-lightning return data about node connectivity to other nodes... was hoping to use it as the backbone for another explorer 13:28 < plankers> mlz file a bug 13:28 < mlz> i'm going to test again and if it happens again, i will 13:28 < fizzwont> "state" : "ONCHAIND_THEIR_UNILATERAL" - ok? 13:29 < newbold> fizzwont: it means they closed the channel manually, I believe 13:29 < fizzwont> i see, thanks 13:29 < fizzwont> if it's closed, will it drop from my peer list...at some point? 13:29 < newbold> I'm assuming that because when I closed mine, it went into ONCHAIND_OUR_UNILATERAL :P 13:29 < newbold> fizzwont: Not sure. Mine that was closed 2+ days ago is still showing there 13:29 < plankers> newbold ive just used the acinq explorer for node connectivity info 13:30 < newbold> plankers: hmm, do they have a mainnet version running? 13:30 < plankers> unknown 13:31 < fizzwont> ok, thx, peer list is a mess, hard to tell what's really active 13:33 < plankers> are you all setting up mainnet nodes? 13:33 < newbold> heh yeah 13:33 < plankers> good luck brave explorers 13:34 < plankers> heres that testnet explorer for those interested https://explorer.acinq.co/#/ 13:34 < fizzwont> this is nothing compared to my losses on early bitcoin testing from 2010 (ehh, i don't need testnet - famous last words) 13:34 < newbold> that's slick 13:34 < newbold> fizzwont: ugh, that makes me cringe :P 13:34 < fizzwont> yes would love that for mainnet 13:34 < plankers> itll probably be made available soon enough 13:36 < mlz> i wouldn't run a node on mainnet if i hadn't played enough on testnet 13:37 -!- princjeblon_ [~princjebl@148.4.wms.cz] has joined #lightning-dev 13:38 -!- princjeblon [~princjebl@148.4.wms.cz] has quit [Read error: Connection reset by peer] 13:39 < plankers> tbh i still need to figure out routing with clightning 13:40 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 13:47 -!- nirved [~nirved@2a02:8071:b58a:3c00:b8b3:341a:4520:4d1c] has quit [Quit: Leaving] 13:54 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has quit [Ping timeout: 256 seconds] 14:04 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #lightning-dev 14:09 -!- booyah [~bb@193.25.1.157] has joined #lightning-dev 14:28 -!- noob123 [4b3909ea@gateway/web/freenode/ip.75.57.9.234] has joined #lightning-dev 14:28 < noob123> Hey I'm currently looking for support to install lightning on my full node. 14:28 < noob123> Everything seems to not work, node is segwit activated 14:29 -!- noob123 [4b3909ea@gateway/web/freenode/ip.75.57.9.234] has quit [Client Quit] 14:31 < mlz> testnet? 14:32 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has joined #lightning-dev 14:38 -!- bryan_w [~is@2600:2108:9:8a90:72a3:5780:f492:1888] has joined #lightning-dev 14:41 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has joined #lightning-dev 14:46 -!- justus [~justus@x4db3887b.dyn.telefonica.de] has quit [Ping timeout: 268 seconds] 14:49 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 14:50 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has joined #lightning-dev 14:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 14:54 < princjeblon_> hmm, i am connected to first network 14:54 < princjeblon_> but not see on https://lnmainnet.gaben.win :/ 14:56 < princjeblon_> or its not updated realtime 15:04 < mlz> what's "first network"? 15:07 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 15:07 < princjeblon_> i now have active 4 peers, "37.59.44.69, "194.71.109.91, "138.68.252.183, "98.186.249.155 15:08 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knonxquuifmwywux] has joined #lightning-dev 15:11 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 15:11 < litch> I have a quick question - I got a node set up, funded it, connected to a few random peers, then opened payment channels with them (mainnet, like $20 in each channel). Then, each of them transitioned to ONCHAIND_THEIR_UNILATERAL. I saw in the lightning node logs messages like: state: CHANNELD_NORMAL -> FUNDING_SPEND_SEEN, state: FUNDING_SPEND_SEEN -> ONCHAIND_THEIR_UNILATERAL, then my node tried to broadcast a transact 15:11 < litch> ion, but that generated `error message: Missing inputs`. In a yes/no answer, did those other nodes just steal my money essentially? 15:12 < cdecker> No, they didn't, they just didn't like keeping a connection open any longer 15:12 < cdecker> So they did a unilateral close, which should return your funds 15:12 <+roasbeef> yeh sounds like they just closed out the channel on their end 15:13 < cdecker> Can you do a `lightning-cli listfunds`? You should see the closing transaction IDs there 15:13 < litch> Oh! Great, yes, now they're starting to come back 15:13 < cdecker> :+1: 15:15 < litch> Quite a learning curve, here, but I'm eager to get this figured out 15:17 < litch> Oh, and like the ppl awhile back, I have a channel opening with SLEEPARK that won't seem to finish opening 15:18 < princjeblon_> litch: same problem. next i try other channels and opened ok. looks as problem on SLEEPARK 15:20 < fizzwont> litch: +1 still stuck 15:23 < princjeblon_> plz do you know, must i add my node anywhere to see on lnmainnet.gaben.win? or where i set my name there and add my node? 15:24 < mlz> no, get off mainnet 15:24 -!- Giuz [5d24b31b@gateway/web/freenode/ip.93.36.179.27] has joined #lightning-dev 15:24 -!- vigorousbearhunt [~vigorousb@gateway/tor-sasl/vigorousbearhunt] has quit [Quit: Leaving] 15:27 < princjeblon_> sorry i not understand? 15:30 -!- neary [~nate@unaffiliated/neary] has quit [Quit: Konversation terminated!] 15:34 < Giuz> Hi all. Same thing as litch here with clightning (unilateral close) but no luck getting them back in "lightning-cli listfunds" so far, is there a way to manually re-add them to the internal wallet db if I have the closing txid? (it has 5 confirms) 15:35 < litch> Giuz it took a really long time for them to re-appear in listfunds 15:35 < Giuz> Oh ok, I understand, I'll wait then, thanks! 15:35 < litch> Though I can't really quantify the "really long time" 15:38 -!- ralphtheninja2 [~lms@c-6469e555.03-130-6e6b701.cust.bredbandsbolaget.se] has quit [Ping timeout: 240 seconds] 15:43 <+roasbeef> if you have to force close, then it depends on what the CSV value was 15:47 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #lightning-dev 15:52 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 256 seconds] 16:00 -!- wxss [~user@185.151.58.115] has quit [Quit: leaving] 16:11 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #lightning-dev 16:11 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Client Quit] 16:21 < cdecker> really long time = 144 blocks (probably) 16:34 < litch> Any hints for getting a channel to actually stay open? Still have not had any luck 16:34 < litch> They keep getting closed by the other side 16:37 < lxer> same 16:38 < fizzwont> i have a few still open, but yes it's hot or miss 16:38 < fizzwont> hit* 16:41 < litch> Ok - thanks fizzwont - does the capacity of the channel matter do you think? 16:41 < litch> Like if instead of trying to open a bunch of 200k sats channels, should I just try for a 500k sat one? 16:41 < fizzwont> not sure, most of mine are 50k 16:42 < litch> Does that mean that after it closes it's essentially gone? 16:43 < fizzwont> you get your money and can re-open a channel 16:47 <+roasbeef> after it closes it isn't gone litch, but if it's a force close, then you may need to wait for a bit of time before the funds are swept back into the wallet 16:47 < litch> But it costs about 50k in fees to actually open/close it seems 16:47 < litch> Like if i open a 200k sats channel, when it closes and i have an unspent again, it's only ~150k 16:48 < litch> There's a good chance I'm misunderstanding something though 16:54 <+roasbeef> depends on how high of fees c-lightning is setting 16:55 <+roasbeef> dunno if you can configure it litch 16:56 -!- zipadee [2f2ae8cc@gateway/web/freenode/ip.47.42.232.204] has joined #lightning-dev 16:57 -!- lxer [~lx@ip5f5bd57e.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 16:57 -!- zipadee is now known as jigawatt 17:00 -!- jb55 [~jb55@S0106bcd1652e9027.vc.shawcable.net] has quit [Ping timeout: 256 seconds] 17:00 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 17:04 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 17:06 -!- princjeblon_ [~princjebl@148.4.wms.cz] has quit [Read error: Connection reset by peer] 17:08 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving] 17:11 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 252 seconds] 17:13 -!- finkan [~finkan@194-103-214-178.kund.ipswe.com] has joined #lightning-dev 17:14 < finkan> did any dev group publish anything about how they solved routing? 17:17 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 17:18 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-knonxquuifmwywux] has quit [Quit: Connection closed for inactivity] 17:18 -!- dabura667 [~dabura667@i114-188-236-55.s41.a027.ap.plala.or.jp] has joined #lightning-dev 17:18 -!- justus [~justus@x4db3e3b7.dyn.telefonica.de] has joined #lightning-dev 17:22 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 17:22 -!- justus [~justus@x4db3e3b7.dyn.telefonica.de] has quit [Ping timeout: 256 seconds] 17:23 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 246 seconds] 17:26 -!- blyat [~blyat@cpe-71-71-200-3.carolina.res.rr.com] has quit [Quit: Leaving] 17:29 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 17:34 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Ping timeout: 268 seconds] 17:35 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 17:36 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #lightning-dev 17:42 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 17:44 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 256 seconds] 17:46 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has joined #lightning-dev 17:46 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has quit [Changing host] 17:46 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #lightning-dev 17:52 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 17:52 -!- finkan [~finkan@194-103-214-178.kund.ipswe.com] has quit [Quit: Leaving] 17:55 -!- Giuz [5d24b31b@gateway/web/freenode/ip.93.36.179.27] has quit [Ping timeout: 260 seconds] 18:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:14 -!- cubancorona [49ca9483@gateway/web/freenode/ip.73.202.148.131] has joined #lightning-dev 18:17 -!- cubancorona [49ca9483@gateway/web/freenode/ip.73.202.148.131] has quit [Client Quit] 18:21 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 268 seconds] 18:21 -!- ebx [~ebx@12.226.6.52] has joined #lightning-dev 18:24 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 18:26 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lightning-dev 18:43 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 18:51 -!- dabura667 [~dabura667@i114-188-236-55.s41.a027.ap.plala.or.jp] has quit [Remote host closed the connection] 19:16 -!- AndBobsYourUncle [AndBobsYou@gateway/vpn/privateinternetaccess/andbobsyouruncle] has joined #lightning-dev 19:19 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 19:19 < windsok> if anyone would like to help test c-lightning on litecoin testnet - https://github.com/ElementsProject/lightning/pull/715#issuecomment-361035002 19:31 -!- AndBobsYourUncle [AndBobsYou@gateway/vpn/privateinternetaccess/andbobsyouruncle] has quit [Read error: Connection reset by peer] 19:32 -!- mughat [~textual@x1-6-28-c6-8e-30-bf-4a.cpe.webspeed.dk] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 19:33 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 19:34 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 19:38 -!- bajohns [bajohns@gateway/vpn/privateinternetaccess/bajohns] has quit [Ping timeout: 256 seconds] 19:49 -!- riclas [~riclas@148.63.37.111] has quit [Ping timeout: 248 seconds] 19:57 -!- riclas [riclas@148.63.37.111] has joined #lightning-dev 20:07 -!- alexann [~Alex@79.125.205.109] has joined #lightning-dev 20:10 -!- Alex_ [~Alex@79.125.251.64] has quit [Ping timeout: 260 seconds] 20:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 20:20 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Quit: Leaving] 20:20 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 20:21 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has joined #lightning-dev 20:33 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qunqmfyikqagahew] has joined #lightning-dev 20:42 -!- Eliel [~jojkaart@104-250-47-212.rev.cloud.scaleway.com] has joined #lightning-dev 20:43 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has quit [Ping timeout: 240 seconds] 20:43 -!- dabura667 [~dabura667@i114-188-236-55.s41.a027.ap.plala.or.jp] has joined #lightning-dev 20:50 -!- jb55 [~jb55@24.87.206.252] has joined #lightning-dev 21:13 -!- litch [~litch@cpe-72-182-55-95.austin.res.rr.com] has quit [Remote host closed the connection] 21:30 -!- dabura667 [~dabura667@i114-188-236-55.s41.a027.ap.plala.or.jp] has quit [Remote host closed the connection] 21:41 -!- jb55 [~jb55@24.87.206.252] has quit [Ping timeout: 268 seconds] 21:54 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #lightning-dev 21:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 22:03 -!- jtimon [~quassel@41.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds] 22:29 -!- riclas [riclas@148.63.37.111] has quit [Ping timeout: 268 seconds] 22:48 -!- mughat [~textual@x1-6-28-c6-8e-30-bf-4a.cpe.webspeed.dk] has joined #lightning-dev 22:57 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 22:58 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lightning-dev 23:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 23:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lightning-dev