--- Log opened Tue May 07 00:00:05 2019
00:20 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #c-lightning
00:22 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
00:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
01:00 < k3tan> "5000 msat delivered with 1 msat fee over 6 hops"
01:00 < k3tan> you're welcoming m-schmoock 
01:00 < k3tan> welcome*
01:27 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:30 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood]
01:31 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
01:45 <@cdecker> fiatjaf: the `pay` plugin only keeps that information internally, decorating the result from `listpayments` with what it knows internally. So upon restart it'll not resume the `pay` attempt and the state is finalized.
01:47 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
01:47 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:06 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 252 seconds]
02:12 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
02:28 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has quit [Ping timeout: 264 seconds]
02:34 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:34 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Client Quit]
02:56 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
03:05 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has joined #c-lightning
03:11 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Ping timeout: 250 seconds]
03:36 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
03:58 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
04:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds]
04:02 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds]
04:03 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
04:16 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:18 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:01 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #c-lightning
06:12 < m-schmoock> k3tan: <3
06:13 < k3tan> lol
06:14 < k3tan> i cant believe it worked first try
06:15 < k3tan> hmmm if i keep sending you 1 msat, constantly, can i take your node offline?
06:17 < k3tan> just keep spamming
06:30 < m-schmoock> k3tan: well, not related to sendinvoiceless as it is a normal routing issue, but eventually the disk will run full if the forwards are not forgotten at some point
06:31 < m-schmoock> (thats why we have fees btw) :D i will chane sendinvoiceless to also account for receivers fee
06:37 < m-schmoock> k3tan: currently the payment of 1msat via snedinvocieless will fail, becuase it wont cover the fees
06:38 < m-schmoock> i still need to patch that the receivers fees are applied ontop, so 1msat payment 'works'
06:38 < m-schmoock> so it will be expensive for the attacker :D
06:44 < molz> i sent 1000 txs with just 1 msat in each tx to someone's LND node once, didn't crash my c-lightning node or his lnd node :D
06:48 < m-schmoock> currently those should fail if the 1msat dont cover the routing fess at the desitnation
06:48 < m-schmoock> sure they went throught ?
06:49 < m-schmoock> cdecker: what is the exact meaning of 'failcodename': 'WIRE_TEMPORARY_CHANNEL_FAILURE'? I have the situation that I try to route a payment and it tries like 100times and fails always at the same node with that error
06:49 < molz> m-schmoock, yes they went thru, we did this a few months ago
06:50 < m-schmoock> Can we optimize this, like when we see 3 tries failing routes at the same 'erring_node' just exclude that?
06:50 < molz> lnd can receive msats but can't create invoices in msat so i was showing the guy lnd could receive 1 msat
06:51 < m-schmoock> lool +1
06:51 < m-schmoock> so you covered the LND routing fees + 1msat
06:51 < molz> yea so after 1000 txs his channel balance got increased by 1 sat :D
06:51 < m-schmoock> sure, but if the LND forwarded the routing without coverage of own fees, that would be a LND 'feature'
06:52 < molz> there was no routing fee, he opened a direct channel to my node
06:52 < molz> hm and i think he sent me a small push_amt, can't remember exactly now
06:52 < m-schmoock> ah ok
07:00 < molz> hm did i say this backward, let me check
07:05 <@cdecker> m-schmoock: is that using the `pay` plugin or some custom code?
07:05 <@cdecker> `pay` should automatically exclude the channel when re-attempting
07:06 <@cdecker> Oh, unless it's the same node reporting the error but always for a different channel
07:07 <@cdecker> We currently don't bias against dysfunctional nodes that fail to announce channel unavailability
07:12 < m-schmoock> cdecker: always for a different channel
07:13 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.4]
07:15 < m-schmoock> cdecker: I think we need to add apply a 'penalty' to a node each time we get a WIRE_TEMPORARY_CHANNEL_FAILURE even for different channels
07:15 <@cdecker> Ok, technically one of the channels may succeed, not sure what to do here
07:15 < m-schmoock> Yes i know
07:16 < m-schmoock> but in some cases, clightning tries to do 100 payments throu one and the same 'giant node' that is simpls disfunctional 
07:16 < m-schmoock> and ends up in giving up
07:16 < m-schmoock> OR we penalize 'giant nodes' :D
07:16 < m-schmoock> that would be cool anyway
07:18 < m-schmoock> the problem is that there are nodes that have 1000 channels and all of them fail
07:18 < m-schmoock> out code can account for this stupidity
07:19 < m-schmoock> *our
07:21 < m-schmoock> cdecker: background: I try using the rebalance plugin, this is sequentially calling rpc.getroute . 
08:16 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has quit [Remote host closed the connection]
08:21 < m-schmoock> cdecker: I finalized work this PR  https://github.com/lightningd/plugins/pull/14 
08:24 -!- kexkey [~kexkey@5.181.233.22] has joined #c-lightning
08:25 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #c-lightning
08:26 < m-schmoock> also, re-check https://github.com/lightningd/plugins/pull/18#discussion_r281668355
08:26 < m-schmoock> *please :D
08:56 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
09:13 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
09:23 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
09:35 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Ping timeout: 250 seconds]
10:07 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #c-lightning
10:36 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds]
11:07 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
12:12 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Remote host closed the connection]
14:51 -!- kexkey [~kexkey@5.181.233.22] has quit [Ping timeout: 246 seconds]
15:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:47 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
16:56 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
18:59 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds]
19:11 < drexl> can I register a webhook once in lightning charge that fires after every payment?
20:05 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
20:07 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds]
20:29 < fiatjaf> drexl, https://github.com/ElementsProject/lightning-charge#post-invoiceidwebhook
20:29 < fiatjaf> oh, it seems no you can't
20:31 < fiatjaf> but it seems so much better to use the websocket or server-sent-events endpoint
20:31 < fiatjaf> --
20:33 < fiatjaf> in which situation getroute will completely ignore my excluded channels? I have some logic that adds the 'erring_channel'/'erring_direction' to the excluded array before trying to 'getroute' again. but getroute is ignoring that and returning a the same route, using the ignored channel. so my 'excluded' array has a dozen of copies of the same channel.
20:35 < fiatjaf> oh, apparently 'erring_direction' doesn't mean the direction of the channel, but rather something else entirely (the node?)
20:35 < fiatjaf> that's confusing.
20:49 < fiatjaf> ok, it doesn't matter. even if adding the channel with the correct direction to after the slash getroute still ignores 'excluded'.
21:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:58 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
22:36 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has joined #c-lightning
23:04 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has joined #c-lightning
23:25 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 252 seconds]
23:40 -!- jtimon [~quassel@181.61.134.37.dynamic.jazztel.es] has quit [Ping timeout: 246 seconds]
--- Log closed Wed May 08 00:00:06 2019