--- Log opened Thu Feb 21 00:00:55 2019 01:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:17 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:57 < bitonic-cjp> If you send out a waitsendpay RPC command, can you perform (and finish) other commands while waiting for the waitsendpay result? 01:58 < bitonic-cjp> I guess technically you can anyway if you use a separate RPC connection for waitsendpay, but it would be nice if you can also do this on a single connection. 01:59 < bitonic-cjp> What I'm actually looking for is a notification service for transaction status changes, and using waitsendpay this way would be a "poor man's notification service". 02:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 02:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 02:26 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:34 <@cdecker> bitonic-cjp: yes, the JSON-RPC is asynchronous, but depending on the client library you may need to open a separate connection 02:35 <@cdecker> We were considering JSON-RPC notifications on the unix socket as well, just didn't get to it just yet. 02:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 02:41 < bitonic-cjp> Oh don't worry about the client side. I do my own JSON-RPC. 02:45 < bitonic-cjp> So, do you think an asynchronous waitsendpay call is the best way to get notified about payment status changes? Are there plans for another interface? 03:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 04:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 250 seconds] 04:25 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 04:27 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 04:52 -!- fiatjaf [~fiatjaf@162.243.220.95] has quit [Quit: ~] 04:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2] 05:25 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 06:12 < bitonic-cjp> hmm, waitsendpay doesn't give me the preimage? 06:15 < bitonic-cjp> The pay command, OTOH, *does* give me the preimage. 06:17 < bitonic-cjp> Unfortunately, the pay command doesn't allow me to specify the route. 06:19 < bitonic-cjp> 'maxfeepercent' and 'maxdelay' are exactly the things I need though, so I'll just go for an asynchonous call of pay. 06:22 < bitonic-cjp> Pay, however, wants a bolt11 input, which is what I don't want. However, pay seems to be implemented as a plugin, so there must be another way to get the preimage... 06:29 < bitonic-cjp> Ah, I see now that waitsendpay *does* give a payment_preimage field. 06:29 < bitonic-cjp> (undocumented it seems) 06:46 < m-schmoock> cdecker: can we do another try for the review? This time git history is as tidy as can be :D 07:29 -!- born2tinkr [~Adium@2600-6c40-6000-0c60-91d7-3d0d-b83a-2a39.dhcp6.chtrptr.net] has joined #c-lightning 07:31 < born2tinkr> Hi everyone, lots of noob here, have gotten c-lightning running on an RBP node and playing around with opening channels and sending lightning payments. If I have an invoice from a remote party that includes an msatoshi amount, am I able to send a payment with a different msatoshi amount to the same user? 07:45 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 07:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 08:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 09:09 -!- harding [~quassel@li1258-130.members.linode.com] has quit [Ping timeout: 250 seconds] 09:10 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:15 -!- harding [~quassel@li1258-130.members.linode.com] has joined #c-lightning 10:43 < t0mix> does anybody know logic behind "listforwards" output? there are 2 kinds.. settled and failed. I'm trying to figure out, why forward might fail. 10:47 < m-schmoock> t0mix: because some hop down the route are failing and a forward at your node can only be valid if the payment went through all hops along the route 10:55 < born2tinkr> Anyone know of any iOS wallet apps that can interact with c-lightning? 11:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 11:10 < t0mix> so, that mean. single node decide which route to take, then try to do "sendpay". it can fail or settle. and my slow performing raspi can happily handle forwards. since it performs badly only when executing "getroute". please, tell me if I am wrong =D 11:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 11:54 -!- born2tinkr [~Adium@2600-6c40-6000-0c60-91d7-3d0d-b83a-2a39.dhcp6.chtrptr.net] has left #c-lightning [] 12:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 12:37 < m-schmoock> t0mix: more or less right, your node poor route discovery is only an issue when you are trying to do a lot of payments originated from your node (not relayed from others) 14:28 -!- wailo [~user@5ED28335.cm-7-3c.dynamic.ziggo.nl] has joined #c-lightning 14:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds] 14:46 -!- wailo [~user@5ED28335.cm-7-3c.dynamic.ziggo.nl] has quit [Remote host closed the connection] 14:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 14:56 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Excess Flood] 15:27 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 16:32 -!- fiatjaf [~fiatjaf@162.243.220.95] has joined #c-lightning 16:36 -!- kexkey [~kexkey@176.113.74.230] has joined #c-lightning 16:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 18:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:17 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 20:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 21:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 21:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 255 seconds] 21:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 21:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 22:40 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 22:48 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 23:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 23:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 23:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 23:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] --- Log closed Fri Feb 22 00:00:57 2019