--- Log opened Sun Jan 05 00:00:47 2020
--- Day changed Sun Jan 05 2020
00:00 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
00:32 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
00:37 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 260 seconds]
01:40 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
01:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
02:33 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
02:38 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 268 seconds]
03:18 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
03:18 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:45 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
04:23 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
04:52 < cdecker>  jb55: we can already use sendonion to send the backups to non-direct peers xD
04:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
04:53 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
05:33 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
06:33 < jb55> cdecker: xD
06:34 < jb55> cdecker: this custommsg thing, can I just spam a node with it? it's just like gossip right? just a different msg id?
06:38 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
06:39 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
07:03 < cdecker> The custommsg should allow you to experiment with custom messages with your direct peers. So it's limit to your local neighborhood, but if more nodes support your custom extension it could also be used to experiment with custom gossip
07:04 < cdecker> If it were a broadcast mechanism, I'd probably have pushed back on the idea, but the way it is localized to your neighborhood makes it safe
07:15 < darosior> Is there a specific reason for using the `io_plan` callbacks to grab the output from bitcoin-cli ? I'm wondering if I could just use `grab_fd()` for the plugin (already used in wait_for_bitcoind() )
07:46 < cdecker> darosior: grab_fd is synchronous, so we are effectively locking everything while waiting for bitcoind to respond in `wait_for_bitcoind`, `io_plan` on the other hand registers interest in future events (output), but hands control back to the `io_loop` which then continues other things
07:46 < cdecker> It's sync vs async IO :-)
07:48 < darosior> Ok so I guess I won't get rid of it! ^^
07:51 < cdecker> Hehe, yeah `io_plan` and its callbacks are the backbone of the async IO framework
09:25 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
09:30 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 268 seconds]
10:46 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
11:12 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
11:13 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
12:31 < vasild> I added c-lightning to the FreeBSD packages. Now installation instructions on FreeBSD become the shortest of all: `pkg install c-lightning`, no manual dependencies handling.
12:49 < darosior> Great !
12:52 < vasild> \o/
13:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
13:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
13:41 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
13:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
13:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
14:17 < cdecker> Great work vasild ^^
14:19 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
14:25 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:49 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
14:56 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning
17:02 -!- My2Sats [457a18ce@ool-457a18ce.dyn.optonline.net] has joined #c-lightning
17:08 < My2Sats> Hello, I have a question regarding the "listtransactions" api which has been added with v0.8.0
17:12 < My2Sats> How can I interpret the "scriptPubKey" in the output?
17:18 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has quit [Ping timeout: 240 seconds]
17:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
17:20 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has joined #c-lightning
17:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
17:51 < My2Sats> Need to figure out from "scriptPubKey", the fund direction. I.e. how much funds have been deposited/removed on-chain, as well the amount which has been directed towards channel funding etc.
18:10 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
18:15 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 260 seconds]
18:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 252 seconds]
18:52 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
18:56 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 240 seconds]
19:31 -!- My2Sats [457a18ce@ool-457a18ce.dyn.optonline.net] has quit [Ping timeout: 260 seconds]
20:04 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Quit: %bye%]
20:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
20:04 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
20:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
20:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
20:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
20:53 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
20:58 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 268 seconds]
21:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
21:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
21:33 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
22:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
23:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
23:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
--- Log closed Mon Jan 06 00:00:58 2020