--- Log opened Sun Mar 17 00:00:18 2019
01:11 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
01:22 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds]
02:04 -!- kexkey [~kexkey@139.28.218.6] has quit [Ping timeout: 246 seconds]
02:46 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:55 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:34 -!- Alterego123 [Alterego12@gateway/vpn/protonvpn/alterego123] has joined #c-lightning
03:35 < Alterego123> what happens if a party force closes a channel? where do funds go?
03:44 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:59 -!- Alterego123 [Alterego12@gateway/vpn/protonvpn/alterego123] has quit [Remote host closed the connection]
04:12 < m-schmoock> ctrlbreak: in this case you might be interested there will be a slight change in the json command result output of setchannelfee as it will support "all" as ID and will return an array of updated channels
04:12 < m-schmoock> if you dont parse result anyway yet, its not important
04:26 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
05:11 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has joined #c-lightning
05:42 -!- dmkathayat [~quassel@ec2-13-233-97-253.ap-south-1.compute.amazonaws.com] has joined #c-lightning
05:49 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 246 seconds]
05:51 < dmkathayat> cdecker: Justin Moon (from the buidl bootcamp) suggested to check out lightning-integration project 
05:52 < dmkathayat> Would love to help, if you can point me to any issues or work items
05:53 < dmkathayat> I took a look at the pending PR on electrum, but apart from adding electrum as a subprocess directly from source, I couldn't make enough sense of it
08:54 -!- Alterego123 [Alterego12@gateway/vpn/protonvpn/alterego123] has joined #c-lightning
09:09 -!- Alterego123 [Alterego12@gateway/vpn/protonvpn/alterego123] has quit []
09:44 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds]
09:51 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
10:04 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
10:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds]
10:17 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #c-lightning
10:27 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2]
10:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
10:54 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
11:00 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
11:59 < SnowGoose> Does anyone have experience trying to use spark wallet to remotely access a c-lightning node?
12:00 < SnowGoose> I have c-lightning and spark-wallet running on my virtual machine, now trying to access it from spark on my host machine running windows desktop
13:10 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
13:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
13:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
13:35 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
13:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
14:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
15:33 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:42 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
15:55 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
16:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:07 < m-schmoock> rusty: https://github.com/ElementsProject/lightning/pull/2470   updated. thx for the input
17:11 < rusty> SnowGoose: Yeah, I use spark-wallet from my Android phone...
17:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]
17:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
17:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
18:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:06 < rusty> m-schmoock: nice work!  Minor feedback, and another PR for you to review :)
18:18 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
18:39 < molz> what does this mean:            "out_msatoshi_fulfilled": 93517963,
18:39 < molz>           "out_fulfilled_msat": "93517963msat",
19:02 < rusty> molz: new format has _msat fields which are all explicitly appended with "msat", unifying all the satoshi / millisatoshi fields.  It's redundant for many.
19:03 < molz> but what is "out_fullfilled.."?
19:04 < rusty> molz: total amount of outgoing HTLCs which succeeded.
19:11 < rusty> In the spec, HTLCs are either failed or fulfilled, hence this language.
19:12 < molz> oh i see, thanks, rusty
19:35 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds]
19:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds]
19:52 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
21:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 272 seconds]
--- Log closed Mon Mar 18 00:00:19 2019