--- Log opened Wed Feb 12 00:00:37 2020
00:19 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has joined #c-lightning
00:33 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
00:36 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
01:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:36 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Quit: Leaving]
01:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
03:08 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 240 seconds]
03:10 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
03:13 -!- fiatjaf [~fiatjaf@2804:7f2:2996:333e:ea40:f2ff:fe85:d2dc] has quit [Remote host closed the connection]
03:14 -!- fiatjaf [~fiatjaf@2804:7f2:2a95:b2c8:ea40:f2ff:fe85:d2dc] has joined #c-lightning
03:28 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
03:51 -!- fiatjaf [~fiatjaf@2804:7f2:2a95:b2c8:ea40:f2ff:fe85:d2dc] has quit [Remote host closed the connection]
03:51 -!- fiatjaf [~fiatjaf@2804:7f2:2997:3549:ea40:f2ff:fe85:d2dc] has joined #c-lightning
04:34 < vasild> My channel with "LNBIG.com [lnd-09]" is stuck in disabled state (listchannels shows it as "active": false) and I wonder how to unstuck it and get it into active state. lightning_channeld seems to be in an infinite loop of init_channel() -> peer_reconnect() -> keep calling sync_crypto_read() in a loop: https://github.com/ElementsProject/lightning/blob/master/channeld/channeld.c#L2366
04:35 < vasild> Every 1 minute sync_crypto_read() returns 001200100000, which I guess is not "interesting" and it gets called again.
04:41 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
04:42 < vasild> 001200100000 is WIRE_PING
04:42 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
04:50 < vasild> It looks like they send us ping, we don't reply anything, they send us ping again after 1 minute and this keeps on going on "forever" and we can't complete peer_reconnect().
04:54 < vasild> The loop in peer_reconnect() repeats because handle_peer_gossip_or_error() returns true from here: https://github.com/ElementsProject/lightning/blob/master/common/read_peer_msg.c#L180
04:58 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
04:58 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has joined #c-lightning
05:01 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Client Quit]
05:02 -!- harding [~quassel@li1228-87.members.linode.com] has joined #c-lightning
05:23 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
05:24 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
05:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
06:08 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
06:30 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
06:31 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
07:01 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
07:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
07:02 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
07:04 -!- Amperture [~amp@65.79.129.113] has quit [Client Quit]
07:50 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
09:38 -!- harding [~quassel@li1228-87.members.linode.com] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
09:41 -!- harding [~quassel@li1228-87.members.linode.com] has joined #c-lightning
10:18 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit []
10:35 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
10:48 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
10:50 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
10:54 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
10:56 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
11:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
11:02 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
11:02 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
11:28 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
11:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
13:49 < darosior> vasild: if I'm not mistaking LND pings you for some time before reenabling forwards to you (really unsure though)
14:01 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
14:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
14:07 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
14:16 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
14:17 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
14:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
14:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:28 < rusty> niftynei, cdecker: we broke Spark again :(
14:29 < rusty> Tried to pay cdecker, timed out, and then "Unknown command 'pay'".  Nothing in logs, but stderr shows "pay: JSON-RPC message does not contain "jsonrpc" field
14:29 < rusty> "
14:36 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
14:37 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
14:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
15:10 <@niftynei> ruff
15:11 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
15:11 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
15:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:14 < darosior> rusty: that's on me... libplugin now enforces JSONRPC2 and requires the JSONRPC field to be present (related https://github.com/ElementsProject/lightning/pull/3442), I thought pyln was the only one to forget it..
15:14 < rusty> darosior: yes, tracked it.
15:14 -!- kristapsk_ is now known as kristapsk
15:14 < rusty> darosior: will revert for rc2, and put bug report into Shesek
15:15 < darosior> Ok
15:50 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
16:26 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has quit [Ping timeout: 260 seconds]
16:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:45 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
16:47 < rusty> darosior: https://github.com/ElementsProject/lightning/pull/3510 (and, while testing that, https://github.com/ElementsProject/lightning/pull/3511)
17:03 < zmnscpxj> #3511 ACK e89b671
17:07 < rusty> All these bugs for simply trying to repay cdecker to make a SWIFT transfer for me!
17:07 < zmnscpxj> Real World Usage
17:08 < zmnscpxj> I think we can merge in #3511, not sure about #3510
17:09 < rusty> zmnscpxj: will wait for Travis, just in case.  Then I'll rc2 if there's nothing else.
17:12 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
17:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
17:17 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
17:17 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
18:15 < rusty> https://github.com/ElementsProject/lightning/pull/3512 too.... Just looked at my listforwards and it's much less informative than I'd hoped!
18:23 < zmnscpxj> #3511 needs a changelog entry as well
18:32 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
19:20 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
19:20 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
19:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer]
19:33 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
19:37 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
19:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
20:16 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
20:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
21:05 < rusty> niftynei: with PoDLE, could you remove from the blacklist by showing that the UTXO was in fact spent?  Well, we could always have a standard "bribe me to unblacklist" I guess.
21:06 < zmnscpxj> that would reveal a mapping between UTXO and PoDLE, which is the whole point of using a PoDLE
21:11 < rusty> zmnscpxj: I guess you can just spend the UTXO and then you're off the blacklist anyway.
21:11 < zmnscpxj> No, I mean: the entire point of the PoDLE is that even if you know the PoDLE you do not know the UTXO
21:11 < zmnscpxj> So in order to get off the blacklist you would have to reveal the UTXO you are referring to anyway
21:12 < zmnscpxj> Which would defeat the point --- we might as well have just shared UTXOs in the open.
21:13 < zmnscpxj> At least the PoDLE can be shared without sharing the UTXO
21:13 < zmnscpxj> but if the owner of the UTXO tries to reuse it they get dinged because some PoDLE blacklists that UTXO
21:13 < zmnscpxj> So I suppose you could have a timestamp on when you receive a PoDLE, then delete them after say one week
21:13 < zmnscpxj> so that at least anyone trying to probe would be rate-limited that way
21:14 < rusty> Yes, we need to ratelimit per node too, somehow.
21:15 < zmnscpxj> Yes, so PoDLEs, when gossiped, are signed by the node that gossips them, the node that gossips them has to have been announced before, which ratelimits the PoDLE gossip as well
21:15 < zmnscpxj> At least that is what I understand, check with nifty and darosior
21:16 < rusty> zmnscpxj: yes, but I can just use one UTXO to create a channel, then spam infinite bogus PoDLE entries.
21:17 < zmnscpxj> yes, I suppose; I think niftynei and darosior were working on that
21:17 < zmnscpxj> they have some kind of mitigation, have not reviewed well
21:17 < rusty> If a node is genuine, then they should only send one PoDLE entry per UTXO they get exposed to in a failed open.  So we can set a reasonable upper bound, say 10,000 per week per node.  If your poor node gets more than tat, you won't be able to broadcast any more.
21:18 < zmnscpxj> Yes, something something something something
21:18 < rusty> But that's OK, since the purpose of PoDLE is not to protect individual nodes (I can always grief a single node if I have 10k utxos to spend), but the network.
21:19 < rusty> Ofc we'll probably ratelimit UTXO exposure anyway: I suggest we just reuse the same UTXO until one tx wins, then move onto the next.
21:19 < zmnscpxj> ...reuse?
21:20 < rusty> yeah, if you're offering to DF, and you have 10 UTXOs, you pick one and keep using it for every channel open which comes in, until one succeeds.
21:21 < zmnscpxj> as in the acceptor?
21:21 < rusty> Yes.
21:21 < zmnscpxj> ah. PoDLE does not limit the acceptor, it limits the opener
21:22 < zmnscpxj> The limiting assures the acceptor that the opener is not just probing everyone to determine what their UTXOs.
21:22 < rusty> Actually, that's a terrible idea.  It would mean that it's actually free to probe, since I'd give Mallory my current UTXO, then he'd just wait for someone else to use it, then try again.
21:22 < zmnscpxj> huh?
21:23 < zmnscpxj> The opener provides a PoDLE, then opens the PoDLE with the UTXO the opener controls
21:23 < rusty> zmnscpxj: Before we discussed PoDLE, this is what I was going to do.
21:23 < zmnscpxj> ah
21:23 < zmnscpxj> yeeeee
21:23 < rusty> zmnscpxj: It's the accepter which want to avoid exposing all her UTXOs.  But this solution is actually worse.  I think we need PoDLE, then.
21:23 < zmnscpxj> ye
21:24 < zmnscpxj> I mean JoinMarket has similar problems, taker == opener, maker == acceptor, so that is why I brought it up
21:25 < rusty> One problem is that you really want to broadcast the PoDLE commit immediately, not wait until failure.  Because otherwise it's trivial to use one UTXO against all the nodes on the network at once.
21:25 < zmnscpxj> yep
21:26 < rusty> But since most opens succeeds, you'd really like to delete them (after some delay to avoid triival timing leaks).  If we ahve nodeid that's trivial I guess.
21:41 -!- mode/#c-lightning [+o rusty] by ChanServ
21:42 <@rusty> Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning  Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.8.1rc2 Logs at http://gnusha.org/c-lightning/
21:43 -!- mode/#c-lightning [-o rusty] by rusty
21:50 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
21:51 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
22:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
22:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
22:47 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
22:47 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
--- Log closed Thu Feb 13 00:00:39 2020