--- Day changed Sun Jan 21 2018 00:07 < xmsx> local/remote feerates are too different: remoteFeeratePerKw=1641 localFeeratePerKw=53760 -- What did I do wrong? 00:14 < e4xit> anyone know how you can change the dev-setfees back to accepting default updates? 00:23 -!- hectorj [5a2abb09@gateway/web/freenode/ip.90.42.187.9] has quit [Quit: Page closed] 00:30 < CubicEarths> bdykesfr_: Is there a list of parameters to pass in at startup? 00:55 < mlz> what does this error mean: 00:55 < mlz> $ lightning-cli fundchannel 025e0ad14ea6cad932641f0a250c52707824b2c16fdf9d1670b2ca874db301a9ad 12000000 00:55 < mlz> "to_self_delay 1441 larger than 432" 01:03 -!- jojeyh [~delphi@2602:306:b8b6:b970:99a5:d356:f613:adc5] has quit [Ping timeout: 276 seconds] 01:24 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 01:37 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 01:37 -githubby:#c-lightning- [lightning] frennkie opened pull request #697: Update to listpeers in README (master...patch-2) https://git.io/vNgyp 01:51 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 01:59 -!- masonV [ac5a0e28@gateway/web/freenode/ip.172.90.14.40] has joined #c-lightning 02:00 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 02:07 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 02:13 -!- masonV [ac5a0e28@gateway/web/freenode/ip.172.90.14.40] has quit [Quit: Page closed] 02:27 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 02:31 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has joined #c-lightning 03:00 -!- provoostenator [~vwDZ2BYsc@mail.sprovoost.nl] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 03:03 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 04:26 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 04:26 -!- CubicEarths [~cubiceart@46.243.136.25] has joined #c-lightning 04:46 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 04:46 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Client Quit] 04:49 -!- CubicEarths [~cubiceart@46.243.136.25] has quit [Ping timeout: 246 seconds] 05:09 < hkjn0> any idea why I'd see '"failed: INVALID 0 (WIRE_TEMPORARY_CHANNEL_FAILURE: Capacity exceeded)"' when 'lightning-cli getpeers' shows a channel with plenty of capacity for the invoice? 05:19 -!- xmsx [b2459dda@gateway/web/freenode/ip.178.69.157.218] has quit [Quit: Page closed] 05:25 -92AACQO0P:#c-lightning- [lightning] cdecker closed pull request #697: Update CLI commands in README (master...patch-2) https://git.io/vNgyp 05:25 -07EAATBPS:#c-lightning- [lightning] cdecker pushed 2 new commits to master: https://git.io/vNgAI 05:25 -07EAATBPS:#c-lightning- lightning/master 0702ee6 frennkie: Update to listpeers... 05:25 -07EAATBPS:#c-lightning- lightning/master 1616fcb frennkie: change getchannels to listchannels 05:28 < hkjn0> nevermind my question, probably there's not enough liquidity further on the route between my node and recipient.. 06:02 -!- humama_ [b2978538@gateway/web/freenode/ip.178.151.133.56] has joined #c-lightning 06:03 < humama_> Hey everyone, please help, how to set lightning node alias while running lightningd on docker? 06:10 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has joined #c-lightning 06:18 -!- humama_ [b2978538@gateway/web/freenode/ip.178.151.133.56] has quit [Quit: Page closed] 06:24 < e4xit> what does this mean: "Peer is in state ONCHAIND_OUR_UNILATERAL" 06:40 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 06:52 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has joined #c-lightning 07:10 -!- e4xit [~e4xit@cpc92716-cmbg20-2-0-cust45.5-4.cable.virginm.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 08:36 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tehrcxmpggddxrlo] has quit [Quit: Connection closed for inactivity] 08:43 -!- kibba [~vince@38.132.119.91] has joined #c-lightning 09:00 -!- chig [4746c6df@gateway/web/freenode/ip.71.70.198.223] has joined #c-lightning 09:06 -!- chig [4746c6df@gateway/web/freenode/ip.71.70.198.223] has quit [Quit: Page closed] 09:10 < kibba> Hi 09:10 < kibba> I have amke test on regtest 09:11 < kibba> with 3 users Alice, Carol & Bob 09:11 < kibba> with 3 instance of c-lightning on localhost, each on a different port 09:12 < kibba> I have a channel between Alice & Carol and a channel between Carol & Bob 09:12 < kibba> Alice can make payment to Carol 09:12 < kibba> But she cannot make payment to Bob via Carol 09:16 < kibba> no route founded 09:16 < kibba> why? 09:36 -githubby:#c-lightning- [lightning] practicalswift opened pull request #702: Adjust log level: Fee limits are ignored by default on testnet (master...ignored-fees-not-unusual-on-testnet) https://git.io/vN2IH 09:45 < kibba> and where are stocked the data? 10:58 -!- kibba [~vince@38.132.119.91] has quit [Ping timeout: 248 seconds] 11:11 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 11:22 -githubby:#c-lightning- [lightning] jb55 opened pull request #705: listpeers: print channel configs (master...list-channel-configs) https://git.io/vN23Q 11:39 -githubby:#c-lightning- [lightning] alaniz3 opened pull request #706: Fixed and updated README RPC doc links (master...master) https://git.io/vN2sD 12:04 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 256 seconds] 13:04 < mlz> what's the command to get a list of channels that your node has? I don't see the command in "help" 13:05 < mlz> "listchannels" is not a command :/ 13:21 < mlz> https://twitter.com/lightningb0t/status/955188344002109443 13:36 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning 13:49 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Quit: WeeChat 1.9] 13:49 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning 13:57 -!- gaxl [aed2007e@gateway/web/freenode/ip.174.210.0.126] has joined #c-lightning 14:03 -githubby:#c-lightning- [lightning] cdecker closed pull request #705: listpeers: print channel configs (master...list-channel-configs) https://git.io/vN23Q 14:16 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qldflzkjwkjdrhfq] has joined #c-lightning 14:19 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:23 -!- gaxl [aed2007e@gateway/web/freenode/ip.174.210.0.126] has quit [Ping timeout: 260 seconds] 15:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:50 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has joined #c-lightning 15:57 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #690: Update README.md with accurate method names (master...method-naming) https://git.io/vNgZJ 15:59 -7IZAAO1Q3:#c-lightning- [lightning] rustyrussell closed pull request #706: Fixed and updated README RPC doc links (master...master) https://git.io/vN2sD 15:59 -7GHABXJ4J:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vN2g3 15:59 -7GHABXJ4J:#c-lightning- lightning/master 73c3175 alaniz: Fixed and updated README RPC doc links 16:01 < rusty> mlz: does allow multiple channels, just not simultaneously to same peer. Kind of a PITA when one closes tho. 16:06 < jb55> I have a suspicion that there is a txfilter bug but I have yet to find it... 16:06 < jb55> my guess is on init but not sure... 16:06 -!- kevin [5e05971f@gateway/web/freenode/ip.94.5.151.31] has joined #c-lightning 16:06 < jb55> I don't see anything wrong though... 16:06 -!- kevin is now known as Guest74891 16:09 < CubicEarths> Is there any spam-script available. It would be fund to have my test-net node try to connect and fund a channel with every node it knows about 16:11 < plankers> +1 for stress testing script 16:13 -!- Guest74891 is now known as kev 16:13 -!- kev is now known as kk_ 16:14 -!- kk_ is now known as kev 16:14 -!- kev is now known as kevin_ 16:14 -!- kevin_ is now known as kvn 16:25 < jb55> lightning-cli listchannels | jq -r '.channels | .[] | [.source,.destination] | .[]' | sort -u 16:25 < jb55> to get all known ids 16:26 < mlz> "Unknown command 'listchannels'" 16:27 < jb55> upgradeee 16:28 < rusty> mlz: that's *so* last week! It was getchannels 16:28 < mlz> lol 16:31 < mryandao> now it works like a breeze 16:31 < mryandao> i think there are issues with some nodes with load 16:31 < mryandao> which causes my clightning node to freeze 16:32 < jb55> yall are missing out if you aren't using my bcalc app: 16:32 < jb55> lcli fundchannel id $(bcalc -n 50000 bits in sats) 16:47 < rusty> jb55: you mentioned you suspect a txfilter bug? I have a channel awiating lockin, yet tx is clearly in chain and 107 deep. 16:50 < jb55> rusty: I have the same situation 16:50 < jb55> also had issues where newaddr funding not getting picked up? 16:50 < jb55> sometimes it works, sometimes not... 16:54 < kvn> jb55 are you running it with bitcoind? 16:55 < jb55> kvn: there's another way to run it? 16:57 < kvn> I have the issue rusty mentioned so I was checking if we where using the same backend. 16:57 < rusty> jb55: Hmm, cdecker is obvious one to ask first, since wallet is his code. 16:58 < rusty> Seems like kvn's problem is different; he managed to disconnect during waiting for funding and we didn't move past it when he reconnected. Def. seeing tx though 17:01 < jb55> think I'll just print out the txfilter keys when the get added and see what's up 17:10 < rusty> kvn https://github.com/ElementsProject/lightning/issues/709 17:26 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds] 17:29 -!- kvn [5e05971f@gateway/web/freenode/ip.94.5.151.31] has quit [Quit: Page closed] 17:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 18:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:02 < ianthius> rusty: i am bringing my old node back up that has comingled mainnet and testnet coins 19:03 < ianthius> rusty: it says 'lightning-rpc' connection refused. how might i overcome this? Is this common when the node is starting up and behing the blocks? 19:03 < rusty> ianthius: yeah, I've been thinking about that. I wonder if we create separate subdirs for diff. networks, and segregate dbs that way. This means we need separate hsm secrets too.... 19:03 < ianthius> I can bring my normal node up and connect via RPC no problem 19:04 < ianthius> rusty: yes, i think that's the best solution. ATM, i am trying to recover my funds 19:04 < rusty> Doesn't usually take long; how long has it been? 19:04 < ianthius> i set a few minutes, but does it refuse connections when it's starting up? 19:05 < ianthius> *been a few minutes.. 19:05 < ianthius> i opened the sql file and set all the outputs from testnet to status '99'.. 19:08 < rusty> No, it scans topology as it starts up... sure it hasn't crashed? 19:08 < ianthius> hoping to just withdraw the funds to my new node, but can't seem to connect to the older node once I brought it up setting the --lightning-dir to the old direcotry. 19:09 < ianthius> it's still in top 19:10 < ianthius> the log just posted another 'adding block' 19:11 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 19:15 < ianthius> rusty: this is all with the same user that i am currently using for the other instance that has been running succesfully on mainnet (which i did bring down temporarily while i try this). Perhaps i should add another user and run it from there? 19:16 < rusty> ianthius: look in /proc//fd and see what RPC file it has open 19:19 < ianthius> it doesn't have any open 19:19 < ianthius> just the log and the database 19:19 < ianthius> rusty: i wonder why it didn't load an RPC? 19:20 < ianthius> rusty: maybe if i kill the node and delete the RPC file it will create a new one? 19:20 < rusty> NO no no... wiat, checking code 19:21 < ianthius> no worries, that's why i asked :) 19:21 < rusty> ianthius: what version BTW? 19:21 < rusty> Assume you have Hello world in the logs... 19:23 < ianthius> how do i tell the version? And I don't understand your hello world question 19:27 < ianthius> I just ran git clone on the main repo earlier this weekend, maybe Thursday.. 19:34 < ianthius> rusty: i don't know if this is related but right before this started when i mistyped my --lightning-dir argument. I typed "lightningd --network=bitcoin --lightning-dir ~/.lighting_old --loglevel=debug > new_log.log &" to start the app 19:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 19:35 < ianthius> *delete the word 'when' in my comment aboce 19:35 < ianthius> *above :) 19:35 < rusty> ianthius: There should be a message in that new_log.log like: 19:35 < rusty> Hello world from %s aka %s #%s (version %s)! 19:36 < rusty> BTW< you did do: ls -l /proc/`pidof lightningd`/fd 19:36 < rusty> Not some other process? 19:38 < ianthius> yes, 19:39 < ianthius> rusty: it was lightningd. it had the logname i had used when starting this instance as well as the DB opened 19:40 < rusty> OK, so there are two circumstances under which it won't load the RPC file. 19:40 < ianthius> lightningd(25647): Listening on 'lightning-rpc' 19:40 < ianthius> lightningd(25647): Hello world from 023322703442cfd1d1fcc20d6564c31653c855beaf5c96bddfecc48b65c2f9dd15 aka ORANGEDEITY #023322 (version v0.5.2-2016-11-21-1591-ga06f0df 19:40 < ianthius> )! 19:41 < ianthius> that was at the top of my log, but that's a hello form another node, no? 19:41 < rusty> No, that's this node. 19:42 < ianthius> the software version on the repo is from nov 2016? 19:42 < rusty> ianthius: No, tha's the last tag. It's actually 1591 commits ahead of that 19:42 < rusty> ianthius: so, is it possible that rpc_filename is empty? Could be in config file or cmdline. 19:43 < ianthius> i didn't specify it at call time, I also don't ahve a config file.. 19:43 < rusty> Otherwise line immediately before hello world should be "Listening on 'lightning-rpc'" 19:44 < ianthius> it was, see my post 10 line sup 19:44 < rusty> Oh, sorry missed it! 19:44 < ianthius> np 19:45 < rusty> That is... weird. OK, how are you at using gdb? 19:46 < ianthius> i've debugged a lot with gdb... in college which wasn't yesterday let me tell you :) 19:46 < ianthius> i'm happy to try or send you the tar of the .lightning folder 19:46 < rusty> ianthius: that's cool, this should be easy. Do 'gdb lightningd/lightningd' in the source dir, then 'attach 19:47 < rusty> Let's go priv to avoid spamming :) 20:06 < CubicEarths> rusty: It is nice to follow along... It's not like this channel is overcrowded 20:15 < rusty> CubicEarths: OK, I think ianthius and I got through that :) 20:16 < CubicEarths> rusty: I've got a question, is there a list of the command line parameters somewhere? 20:16 < rusty> ianthius: OK, so if there are no outstanding channels, just withdraw all 20:16 < rusty> CubicEarths: --help has one... 20:16 < ianthius> what qualifies as an 'outstanding channel'? 20:16 < rusty> ianthius: look in getpeers? 20:16 < CubicEarths> I saw that one, but it didn't seem complete 20:16 < ianthius> yes, i have two 20:17 < rusty> But they're testnet so you don't care? 20:17 < ianthius> correct 20:17 < rusty> ianthius: great, then 'withdraw all' 20:17 < ianthius> but will it impeed with the mainnet withdraw is some way? 20:17 < rusty> ianthius: nope. Just if there were channels, we'd shut them down first so you get all your funds. 20:18 < ianthius> k. thx. 20:18 < rusty> (withdraw only pulls from wallet) 20:18 < ianthius> rusty: i think cli should know to communicate with the lightningd despite the working directory change, since it's the only node running on the box 20:18 < ianthius> also, i don't need to include --network on the CLI so why would i need --lightning-dir? 20:19 < rusty> ianthius: it communicates via the socket in that directory though... 20:19 < ianthius> i see, so it can't communicate with teh daemon at all if it doesn't have permissions, and it only gets permission in the vanilla case due to knowing the default dir? 20:21 < rusty> ianthius: Not quite. lightningd creates a socket in that dir so others can communicate with it, eg. lightning-cli. 20:21 < rusty> I do not use a TCP socket, because I want pid protection and permissions and local access only etc. It's old-school UNIX. 20:22 < rusty> (technically, you can use --rpc-file= directly, but that defaults to /lightning-rpc which is usu what people wnat. 20:23 < rusty> But please file a bug for a clearer error in this case! 20:23 < ianthius> sounds good. Also thanks. my funds i THINK are on their way :) 20:24 < ianthius> thx 20:24 < ianthius> now i get to open MOAR channels! ;) 20:24 < rusty> ianthius: great! Congratulations on unlosing your funds :) 20:29 < CubicEarths> rusty: is there another list of command line parameters other than --help? --help doesn't seem to have an exhaustive list 20:31 < ianthius> CubicEarths: have you used 'lightning-cli help'? 20:31 < CubicEarths> yes 20:31 < ianthius> and 'lightningd --help' the both show different things 20:31 < ianthius> i think some things are undocumented 20:32 < CubicEarths> oh, let me check both 20:33 < CubicEarths> I see now, thanks 20:35 < ianthius> np 20:40 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has joined #c-lightning 20:40 < CubicEarths> I think it would be cool to make a standalone 'watcher' program, that just kept track of all the channel states, watched the blockchain for confirmation of any earlier state, and broadcast the most recent if noticed that. 20:56 < ianthius> can lightningd be launched in daemon mode like bitcoind? e.g. -daemon? that seems useful.. 21:07 < ianthius> i have all these failed channel openings in 'getpeers' how do i close those since they are with a peer i DO have a channel with and the ID is the same as the open channel, and I am afraid it will close the channel i have open with them.. 21:17 < windsok> have not checked my testnet node for a couple of days, now it has a ton of peers in OPENINGD state, many of them duplicates from the same peerid. Looking into it, but has anyone seen the same 21:21 < ianthius> that is the state my mainnet peers are in from failed channel opennings due to fee mismatches 21:21 < ianthius> seem's the peers never error out and are listed permanently? 21:24 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Read error: Connection reset by peer] 21:24 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 21:43 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 21:44 -!- CubicEarths [~cubiceart@46.243.136.38] has joined #c-lightning 21:45 -!- CubicEar_ [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 21:48 -!- CubicEarths [~cubiceart@46.243.136.38] has quit [Ping timeout: 246 seconds] 22:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 22:52 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has quit [Remote host closed the connection] 23:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 23:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 268 seconds]