--- Log opened Thu May 21 00:00:28 2020
00:09 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 252 seconds]
00:10 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
00:15 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
00:20 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 258 seconds]
00:27 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
00:37 -!- liberliver1 [~Thunderbi@x4db7c771.dyn.telefonica.de] has joined #c-lightning
00:38 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 260 seconds]
00:38 -!- liberliver1 is now known as liberliver
00:51 -!- liberliver [~Thunderbi@x4db7c771.dyn.telefonica.de] has quit [Remote host closed the connection]
00:54 -!- liberliver [~Thunderbi@x4db7c771.dyn.telefonica.de] has joined #c-lightning
00:58 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
00:59 -!- jonatack [~jon@37.170.253.61] has joined #c-lightning
01:09 -!- liberliver1 [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
01:11 -!- liberliver [~Thunderbi@x4db7c771.dyn.telefonica.de] has quit [Ping timeout: 264 seconds]
01:12 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
01:12 -!- liberliver [~Thunderbi@x4db7c771.dyn.telefonica.de] has joined #c-lightning
01:14 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
01:14 -!- liberliver1 [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 260 seconds]
01:53 -!- jonatack_ [~jon@37.167.18.204] has joined #c-lightning
01:57 -!- jonatack [~jon@37.170.253.61] has quit [Ping timeout: 256 seconds]
02:02 -!- jonatack_ [~jon@37.167.18.204] has quit [Quit: jonatack_]
02:02 -!- jonatack [~jon@37.167.18.204] has joined #c-lightning
02:16 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
02:21 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 264 seconds]
03:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
03:04 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
03:18 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
03:18 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
03:55 < trobjo> I have not looked closely at the code, but does the rebalance and jitrebalance plugins aim to fulfill the same goal?
03:55 < trobjo> We just want to balance our channels, but I assume I will still have to write some checking logic
04:03 <@cdecker> trobjo: jitrebalance will defer any rebalancings to a time when they are needed, minimizing the cost, but still offering the same benefits as apriori rebalancing when it comes to forwarding payments
04:03 <@cdecker> When forwarding we look at what capacity we'd need to forward the payment, then rebalance just-in-time (hence the name) so that the payment can go through. It has more information about the required capacity and can be more efficient than just flatly rebalancing all channels all the time
04:19 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
04:53 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
06:06 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
06:17 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
06:21 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 240 seconds]
06:31 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
06:41 < trobjo> In the original rebalance plugin, the @plugin.method decorator makes the function beneath it available on the command line.
06:42 < trobjo> So that we can manually run `lightning-cli rebalance` when we need to rebalance our channels. 
06:43 < trobjo> But I see no such thing in the jitrebalance. And the documentation is still quite sparse.
06:43 < trobjo> Does it mean, the plugin will rebalance automatically, or will I have to call @plugin.async_hook("htlc_accepted")?
06:58 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
06:58 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
07:04 <@cdecker> trobjo: exactly, rebalance exposes that method to the JSON-RPC so you can make manual adjustments, while jitrebalance works automatically whenever an HTLC comes in
07:07 < trobjo> That is pretty cool! I am going to try it out now.
07:20 <@cdecker> Feedback is always welcome, there is certainly room to improve ^^
07:57 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
08:18 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
08:23 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
08:33 -!- fiatjaf [~fiatjaf@2804:7f2:2a81:6c39:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 240 seconds]
08:35 -!- fiatjaf [~fiatjaf@2804:7f2:2a81:6c39:ea40:f2ff:fe85:d2dc] has joined #c-lightning
08:41 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
08:41 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
08:47 < sword_smith> I have a weird situation. I have made a channel from the BLW software on my Android phone to my lightning node. I can send from BLW to my c-lightning node but not the other way. The problem I get is "Could not find a route". The BLW software generates invoices like this: 
08:47 < sword_smith> lnbc160n1p0vd9jvdqqcqzgapp5t4qvsg7yhnwmeuajnsyg30vxc86mtvryn3lve3sc4va2v7c3r5qqxqyz5vprzjqf720ngdm34xrj4u76l0n8ulwuwuvce5cef6jr2sjcx3dsl7vu4r6zfw2qqqw8gqqqqqqqfvqqqqqqcqpcpkleuel985jvetfguqgav8uhdks4842ekd3xppart3v6uur425yx42js9447fk0257z0ltx6lc7a43lmgvs662sfew3u550z6veh77spcgefy2
08:50 < sword_smith> Parsing this invoice tells me that the payee pub key is 03259c7a586153014e4336d556c7579d69a189eeccbfac5e472010eee3d6dadc5c. 
08:50 < sword_smith> But I have no channel with this pub key 03259...
08:52 < sword_smith> Calling `listfunds` (in c-lightning) the BLW channel looks like it is made to "02216c4b12b5fdf0635eabea6c0867f77e4ecdfe2938e140c1a3514c38cfaa7698".
08:52 < sword_smith> Which I cannot find in the BLW-generated invoice.
08:54 < darosior> And what tells BLW about its own node id ?..
08:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
08:57 < sword_smith> Yes, I tried looking for that in the BLW program but I couldn't find it. 
08:57 < sword_smith> This is the funding txid: f24c9b30f1e1a7d60dcd7c45a895b84f8ff879d9ca0ffc4b78d2ea386d763d45
08:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
09:02 < sword_smith> c-lightning node ID is: 027ca7cd0ddc6a61cabcf6bef99f9f771dc66334c653a90d50960d16c3fe672a3d
09:10 < sword_smith> I found this bug report on the BLW project: https://github.com/btcontract/lnwallet/issues/18
09:11 < sword_smith> But I don't know if this is a c-lightning issue or a BLW issue.
09:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] 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:38 < fiatjaf> sword_smith: thank you
09:38 < fiatjaf> you just solved the bug
09:40 < sword_smith> I did?
09:40 < fiatjaf> I think you did
09:40 < fiatjaf> I believe BLW issues a different nodeid on every invoice
09:40 < fiatjaf> and that would work if someone tried to pay the invoice from any other node
09:40 < fiatjaf> except the node you're connected to
09:41 < fiatjaf> because on that case c-lightning will probably use the nodeid to look instead of the channel in the invoice hint
09:41 < fiatjaf> let me try and pay your invoice
09:45  * sword_smith is sitting on the edge of his seat
09:46 < fiatjaf> well, I can't pay it because all my channels are broken
09:48 < sword_smith> Ah, I see.
09:50 < fiatjaf> but it should work
09:52 < fiatjaf> well
09:52 < fiatjaf> I see this was all said on the issue you linked
09:58 < sword_smith> So is this a bug in c-lightning or in BLW?
09:58 <@cdecker> I verified that route hints work just a couple of days ago, might be an issue with how BLW encodes routehints?
09:59 <@cdecker> Can you open an issue on our repo, including the invoice, the output of pay, and paystatus for that invoice?
10:01 < sword_smith> The invoice was reated on BLW so I don't know if `paystatus` has the information you are looking for: `lightning-cli paystatus <invoice>` --> { "pay": [] }
10:02 < sword_smith> I will open an issue 
10:02 <@cdecker> Strange, it should show the failed payment attempts, unless we fail right at the first getroute call
10:03 <@cdecker> Yeah, I'll look at it asap
10:05 < fiatjaf> if you do getroute to yourself you should get an empty array
10:05 < fiatjaf> wouldn't that make it work?
10:19 < sword_smith> https://github.com/ElementsProject/lightning/issues/3739
10:19 < sword_smith> cdecker: Sorry. The software I wrote calls getroute before attempting to pay. That's why it didn't show up.
10:20 < sword_smith> I called pay manually, after that it *did* show up under `paystatus`.
10:22 <@cdecker> Phew, that makes sense now :-)
10:25 <@cdecker> Hm, interesting, just by glancing at it it seems like we're dropping a routehint because it includes ou local node?
10:26 <@cdecker> sword_smith: can you also add the output of `getinfo` and `listpeers`? That hopefully gives us all the necessary context
10:26 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
10:26 < sword_smith> cdecker: Yes
10:33 < sword_smith> Updated
10:47 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
10:47 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
11:05 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
11:32 -!- jasan [~jasan@tunnel509499-pt.tunnel.tserv27.prg1.ipv6.he.net] has quit [Ping timeout: 240 seconds]
11:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
11:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
11:59 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
12:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
12:17 -!- jonatack_ [~jon@184.75.221.203] has joined #c-lightning
12:18 -!- jonatack [~jon@37.167.18.204] has quit [Ping timeout: 256 seconds]
12:23 -!- jonatack_ [~jon@184.75.221.203] has quit [Quit: jonatack_]
12:24 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
13:46 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
13:52 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
13:53 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
13:53 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
14:09 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
14:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
14:40 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 260 seconds]
15:16 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
15:53 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
15:53 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
15:53 -!- ctrlbreak_MAD [~ctrlbreak@159.2.182.106] has joined #c-lightning
16:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:18 -!- 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]
19:21 < fiatjaf> I have a bunch of pending htlcs on various channels
19:22 < fiatjaf> mostly "in"
19:22 < fiatjaf> according to `listpeers`
19:22 < fiatjaf> and they have no counterpart with the same payment_hash in a different channel
19:33 < fiatjaf> does that mean they are waiting for my node to resolve them?
20:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
20:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:24 -!- vasild_ is now known as vasild
22:50 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
22:54 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 256 seconds]
23:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
23:23 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
23:46 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
--- Log closed Fri May 22 00:00:28 2020