--- Log opened Mon Oct 15 00:00:37 2018
00:31 -!- bitonic-cjp [~bitonic-c@80.100.203.151] has joined #c-lightning
04:06 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
04:09 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds]
05:08 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning
05:08 -!- reallll is now known as belcher
07:19 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
07:19 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
08:02 -!- kabaum_ [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning
08:29 -!- bitonic-cjp [~bitonic-c@80.100.203.151] has quit [Quit: Leaving]
09:52 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
09:55 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
09:57 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
10:00 < michaelsdunn1> How do I configure c-lightning to expose the JSON-RPC API on a specific port?
10:11 < spinza> following on from my post yesterday:  channel was in CHANNELD_AWAITING_LOCKIN state (but funded).  I closed it but now it stays in "CHANNELD_SHUTTING_DOWN:They've confirmed funding, we haven't yet. AND They've sent shutdown, waiting for ours"
10:11 < spinza> What next?
10:13 < spinza> It's been in the CHANNELD_SHUTTING_DOWN for almost 24h now
10:28 < grubles> michaelsdunn1, did you check --help
10:30 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-iaeihkgdlmmskdhm] has joined #c-lightning
10:31 < michaelsdunn1> I see, looks like I can do --rpc-file
10:31 < michaelsdunn1> thanks
11:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
11:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
11:52 < spinza> anyways to get money out of my channel that's stuck in CHANNELD_SHUTTING_DOWN
11:55 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
11:55 <@cdecker> michaelsdunn1: c-lightning doesn't expose its JSON-RPC via the network, it's a unix socket
11:55 <@cdecker> spinza: yes, you can force close
11:56 < spinza> close id force?
11:57 < spinza> is force just the word force?
11:57 <@cdecker> lightning-cli -k force=true id=[nodeid]
11:57 <@cdecker> That should work
11:58 <@cdecker> It'll try a collaborative close, and if that doesn't terminate in 30 seconds it'll do a unilateral
11:58 <@cdecker> The unilateral will return funds in ~24h depending on the parameters the peer enforces
11:58 < spinza> ok not seeing -k in the --help
11:59 < spinza> i closed the channel about this time yesterday
11:59 <@cdecker> The -k is simply switching to key-value mode 
11:59 <@cdecker> It's lightning-cli specific, not lightningd
11:59 <@cdecker> Hence you need lightning-cli --help to see its options
12:00 < spinza> it's not listed under cli but i'll try it
12:00 <@cdecker> Key-value mode is just easier to work with rather than the positional options, but this'll also work: lightning-cli close [nodeid] true
12:00 < spinza> ah ok
12:04 < spinza> cdecker, thanks that generated a new tx that seems to be paying me back :)
12:40 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-iaeihkgdlmmskdhm] has quit [Quit: Connection closed for inactivity]
13:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
13:28 <@cdecker> Great, glad it worked out in the end
13:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
14:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
14:17 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
15:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:38 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.2]
15:58 -!- deusexbeer [~deusexbee@080-250-075-064-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
17:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
17:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
18:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]
19:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
21:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds]
22:11 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]
--- Log closed Tue Oct 16 00:00:38 2018