--- Log opened Fri Jan 03 00:00:56 2020 00:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 00:26 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Ping timeout: 250 seconds] 00:32 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 00:45 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #c-lightning 00:53 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning 00:55 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Read error: Connection reset by peer] 01:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.6] 01:32 < darosior> cdecker: What do you think of keeping the `getfilteredblock` logic in `lightningd/bitcoind` 01:32 < darosior> This would just add the need for `gettxout` plugin-side 01:33 < darosior> This avoid to replicate the logic into another plugin 01:34 < darosior> At least until we do something that it can really optimize like `getoutputbyscid` 01:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 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:01 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] 02:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 265 seconds] 02:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 02:52 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 02:53 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 03:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 03:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 03:41 -!- shupfel [~Bohphah3@92.117.141.1] has joined #c-lightning 03:45 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Quit: ZNC - https://znc.in] 03:47 -!- molly [~molly@unaffiliated/molly] has joined #c-lightning 03:49 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #c-lightning 03:50 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 04:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 04:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 04:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 04:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 04:14 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 04:31 -!- jonatack [~jon@134.19.179.163] has joined #c-lightning 04:42 -!- jonatack [~jon@134.19.179.163] has quit [Ping timeout: 260 seconds] 04:43 -!- jonatack [~jon@134.19.179.163] has joined #c-lightning 05:48 -!- jonatack [~jon@134.19.179.163] has quit [Ping timeout: 268 seconds] 06:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 07:05 -!- mol [~molly@unaffiliated/molly] has joined #c-lightning 07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.] 07:07 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds] 07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has joined #c-lightning 07:17 < cdecker> darosior: sounds good to me, a plugin could actually store filtered blocks for the case that we actually request multiple outputs from the block 07:18 < cdecker> Let's get a minimal one working, and then we can deal with the efficient implementations 07:20 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 07:38 < darosior> Yep ! 07:41 < darosior> I thought of something, which could (once again :) ) be overkill, but we could combine both the efficiency of the filtered block and the expliciteness of getoutputbyscid. The plugin could poll and cache filtered blocks, then directly serve outputs by scid when requested by lightningd. I wonder if this requires a new DB though.. 07:49 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 07:52 -!- mol [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 09:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:58 < jb55> so now that we have the data_version thing I think I might take a stab at a backup plugin. I wonder if I could send streaming backups over LN? Then any node with the plugin could be a backup server? 10:00 < jb55> might be crazy but would give me a chance to play with createonion/sendonion 10:28 < jb55> think I might work on a rust plugin api first, doesn't look like there are any rust plugins yet? 10:34 <@niftynei> sebastian had a rust plugin framework, not sure if that's what you're talking about. afaik it hasn't been used for anything tho 10:35 <@niftynei> not sure what state the framework is in, let me see if i can find it 10:45 < jb55> niftynei: yeah that's what I was referring to 10:55 < jb55> found it here https://github.com/sgeisler/clightning-plugin-api 10:56 <@niftynei> yep that's the one 11:01 < jb55> oh I missed https://github.com/ElementsProject/lightning/pull/3315, looks like I might need that 11:13 -!- vincenzopalazzo [~vincenzop@host148-246-dynamic.36-79-r.retail.telecomitalia.it] has joined #c-lightning 11:55 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 11:55 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 12:41 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning 12:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 258 seconds] 13:04 < cdecker> jb55: I have the scaffold of a backup plugin that writes to a file incrementally here https://github.com/lightningd/plugins/tree/backup 13:04 < cdecker> It still needs the cli tool to initialize the file, but it seems to be working ok. The interface should also be flexible enough to add other backends as well 13:05 < jb55> oh nice 13:11 < jb55> cdecker: we can recover from the "c-lightning is one or more writes ahead" case right? via a new snapshot? 13:15 < cdecker> I'd prefer not to, since that'd mean we weren't running for a while which can be unsafe (if we lost writes, and ran without a backup) 13:16 < cdecker> That's why I am a bit pedantic in that case 13:18 < jb55> cdecker: so in that case you would just shut down clightning, wipe the log and start over? 13:18 < jb55> I guess that's all you can do... the other cases seem reasonable as well 13:28 < jb55> cdecker: now just need a backend that sends the log as a custommsg :) 13:28 < jb55> replicated backups over ln! 13:30 < jb55> just not sure how to charge for it.. it would be cool if you just pay per log but I don't see how that would work since it would create a recursive loop 13:37 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 13:40 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 13:47 -!- paultroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection] 14:48 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:07 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 15:11 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 15:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:06 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds] 16:16 -!- vincenzopalazzo [~vincenzop@host148-246-dynamic.36-79-r.retail.telecomitalia.it] has quit [Remote host closed the connection] 16:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 17:18 -!- shupfel [~Bohphah3@92.117.141.1] has quit [Ping timeout: 268 seconds] 18:26 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection] 19:38 -!- fiatjaf1 [~fiatjaf@2804:7f2:2996:5492:ea40:f2ff:fe85:d2dc] has joined #c-lightning 19:41 -!- fiatjaf [~fiatjaf@186.213.100.35] has quit [Ping timeout: 240 seconds] 20:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning [] 20:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning 21:25 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 21:25 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 21:32 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 268 seconds] 22:49 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 23:30 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 23:39 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] --- Log closed Sat Jan 04 00:00:56 2020