--- Log opened Wed May 20 00:00:26 2020
00:16 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:19 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Read error: Connection reset by peer]
00:19 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
00:24 < Educob2> But command getroute returns a valid route (I am trying to pay just with pay command)
00:38 < Educob2> using sendpay I get error "UNUSUAL 0263eae97783d84a19acf6ee7378ac963d15401eb8541d3b71c6dbc1121cc3e606-channeld-chan#1: Adding HTLC too slow: killing connection"
00:38 < Educob2> and "INFO 0263xxxx-chan#1: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)"
01:52 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
01:53 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
02:29 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
02:31 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
02:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
02:38 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
02:57 < sword_smith> I think there is a plugin to handle liquidity by maintaining channels in c-lightning. What is it called, and which one should I use?
03:05 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
03:19 <@cdecker> There are a couple that manage your channel balances, for example the drain plugin will minimize your balance so you can close the channel with minimal fees (one output only)
03:19 <@cdecker> Then there's the jitrebalance plugin that tries to rebalance if necessary to forward a payment
03:20 < darosior> And rebalance which allows you to choose which channel pair to use
03:20 <@cdecker> The rebalance plugin will try its best to rebalance your channels according to your instructions
03:23 <@cdecker> fiatjaf: I'm currently reworking the pay plugin to be more modular and allow us to experiment building extensions in C
03:24 <@cdecker> And I hop to eventually port that same mechanism to pyln so building custom `pay` variants becomes easier
03:25 <@cdecker> Educob2: are the two nodes on the same network / machine? Any chance we could get some more logs (pastebin / gist)?
03:28 < sword_smith> We just upgraded from 0.7.2 to 0.8.2 -- I just verified that invoice generation, receiving, and sending all still works.
03:33 < sword_smith> I think we are only using the webhook (callbacks for receiving txs) and sparko (HTTP endpoints for node interaction) plugins atm.
03:36 < sword_smith> Our web wallet currently uses Bitcoin Core for onchain txs and c-lightning for offchain, but wouldn't it be smarter to use c-lightning for both?
03:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
03:44 < Educob2> the two nodes are on the same computer
03:44 < Educob2> How do I use pastebin / gist? Thanks.
03:45 < sword_smith> wrt liquidity management I am interested in the one the that has the highes degree of automation.
03:45 < sword_smith> The one that requires the least user interaction.
03:52 <@cdecker> Then jitrebalancing is likely what you want
03:52 < sword_smith> Cool
03:52 < sword_smith> Thanks
03:53 <@cdecker> It won't do much if your node doesn't forward, but it can increase chances of successful forwardings significantly
04:04 < Educob2> Can you please tell me what information should I give you to see why I can't pay fro node2 to node 1 in the same computer? Thanks.
04:04 < bitdex> kj/exit
04:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:19 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
04:19 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
04:20 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
04:30 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
04:30 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
04:35 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
04:53 < sword_smith> It seems that the datamodel sent from Fiatjaf's webhook has changed in the interim.
05:17 < fiatjaf> sorry, sword_smith, it did change, now it should sent exactly what it gets from lightningd
05:17 < fiatjaf> send*
05:18 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 265 seconds]
05:18 < fiatjaf> that makes things simpler I hope, but yeah breaking compatibility sucks
05:19 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
05:20 < fiatjaf> sword_smith: if you're using sparko the new version also sends all the events (same as webhooks) as server-sent events. you just open a connection to /stream using one of these SSE libraries and should be good. I'm finding that easier to deal with than webhooks.
05:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
05:38 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
05:50 -!- Educob2 [5a4ae098@90.74.224.152] has quit [Quit: Ping timeout (120 seconds)]
05:57 -!- Educob2 [5a4ae098@90.74.224.152] has joined #c-lightning
06:20 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
06:22 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
06:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
06:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
07:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:02 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
08:03 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
08:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
08:21 < Educob2> I can send from node1 to node2 but not from node2 to node1. I get error 205 Could not find a route
08:21 < Educob2> Adding HTLC too slow: killing connection
08:22 < Educob2> Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)
08:24 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
08:35 < darosior> Educob2: did you just found the channel ? If so you don't have enought capacity on the l2 --> l1 edge
08:36 < darosior> Even if you already paid l1 --> l2 it's added to the reserve (funds non spendable on the channel, basically)
08:36 < Educob2> No. I have already sent several times from node1 to node2. It has over 400 satoshis and I am trying to send 15 satoshis
08:36 < Educob2> "funds non spendable on the channel" Why not? When can I send back?
08:36 < darosior> How much is the channel ?
08:37 < Educob2> 2000000000msat
08:37 < darosior> Someone may correct me but iirc the channel is 1% so you need to send 0.01 * channel capacity + funds to be received
08:37 < Educob2> Thanks. I'll try.
08:37 < darosior> How much did you send to l2 ?
08:37 < darosior> Ok
08:38 < Educob2> not really sure cause in one of the output I see 417satoshis and in other 425sats.
08:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:38 < Educob2> so 1% should be 2000 sats.
08:39 < Educob2> 20000 sats
08:39 < Educob2> I am sending that now.
08:41 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
08:42 < Educob2> You were absolutely right!!! Thanks.
08:42 < Educob2> 1% seems to be the amount. LN has plenty of limitations.
08:55 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:21 -!- trobjo [troels@bitcoinfundamentals.org] has joined #c-lightning
09:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:23 -!- vasild_ is now known as vasild
09:33 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
09:36 < trobjo> On c-lightning v0.8.2.1 with fiatjafs sparko plugin 2.0, I get the following error, when I try to start the lightning service:
09:36 < trobjo> DEBUG plugin-manager: started(29194) /usr/local/libexec/c-lightning/plugins/sparko
09:37 < trobjo>  **BROKEN** plugin-sparko: Could not register method "invoicewithdescriptionhash", a method with that name is already registered
09:37 < trobjo> INFO plugin-sparko: Killing plugin: /usr/local/bin/../libexec/c-lightning/plugins/sparko: Bad response to getmanifest.
09:37 < trobjo> Does anybody have a clue about what I am doing wrong?
09:53 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
10:15 <@cdecker> trobjo: that happens if you add the plugin twice, or (unlikely in this case) two plugin attempting to register the same method name
10:16 <@cdecker> trobjo: you can check whether one instance is still running by calling `lightning-cli help` and see if the method is listed in the help text
10:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
10:45 < trobjo> It is not listed there. I suspect it is because sparko is launched automatically (by a dependency?) before I call it in the config. 
10:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
10:51 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
10:52 < trobjo> I was a dork, and didn't read the documentation properly :-) 
11:13 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
11:16 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
11:18 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
11:18 <@cdecker> Hm, how so? Could be helpful to know what the issue was for the future :-)
11:22 < trobjo> Absolutely! The issue was that sparko was already placed in the default plugin dir, so lightningd was trying to start it twice. 
11:22 < trobjo> Interestingly, the log did not give me any warnings/errors for any of the other duplicate plugins.
11:23 <@cdecker> Interesting, we should probably deduplicate automatically picked up plugins and those from the cli anyway 
11:24 <@cdecker> Thanks for reporting ^^
11:24 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
11:24 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
11:38 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
11:54 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
11:59 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 260 seconds]
12:06 < sword_smith> Working with c-lightning and the associated plugins is easier than to work with the Ethereum node that I have worked with, geth. But it's not quite as smooth/backwards compatible as Bitcoin Core -- yet. 
12:06 < sword_smith> But I am glad to see that fiatjaf's plugins are still maintained and are not being deprecated!
12:08 < sword_smith> You are doing a great job, fiatjaf! webhook just required a pretty small change in our deposit system to work, and sparko didn't require any change at all in our upgrade from 0.7.2 to 0.8.2.
12:12 < sword_smith> We upgraded c-lightning *and* the plugins.
12:12 < sword_smith> It's really cool that your software is this easy to work with.
12:13 <@cdecker> Thanks sword_smith, we're doing our best to become a stable foundation to build on, and so far the community has been awesome at picking it up and running with it ^^
12:40 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning
13:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
13:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 272 seconds]
14:11 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
14:16 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 256 seconds]
14:49 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
15:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
15:41 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
15:41 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
15:44 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: leaving]
15:45 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
16:09 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds]
16:13 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Quit: leaving]
16:15 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
16:17 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
16:19 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
16:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:32 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
16:42 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
17:37 -!- Educob2 [5a4ae098@90.74.224.152] has quit [Remote host closed the connection]
18:13 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 260 seconds]
18:58 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
19:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
19:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
19:21 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
19:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
19:26 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
19:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 260 seconds]
19:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
19:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:13 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
20:19 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 256 seconds]
20:28 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
20:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:23 -!- vasild_ is now known as vasild
22:13 -!- berndj [~berndj@azna.co.za] has quit [Ping timeout: 265 seconds]
22:24 -!- berndj [~berndj@azna.co.za] has joined #c-lightning
22:34 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
22:52 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds]
22:57 -!- jonatack [~jon@213.152.162.79] has joined #c-lightning
23:14 -!- jonatack [~jon@213.152.162.79] has quit [Ping timeout: 264 seconds]
23:47 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
--- Log closed Thu May 21 00:00:28 2020