--- Log opened Thu Jul 08 00:00:00 2021
00:38 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning
00:43 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 252 seconds]
01:14 -!- kon__ [~kon@p200300d4a714b10038bc1e47002358f1.dip0.t-ipconnect.de] has joined #c-lightning
01:16 < nathanael> i need some help i have the following in my logs: https://tmp.dalliard.ch/60e6b4283c1a541e.txt
01:16 < nathanael> i think i've setup my node the wrong way (i could reach out, but somehow my node was not reachable, i tried to setup ipv4, ipv6 and torv3)
01:16 < nathanael> now on person still could manage to open a channel but that changed now to closing and settling onchain
01:16 < nathanael> /s/on/one/
01:28 < nathanael> letting the channel settle onchain and opening a new one is probably what we will do
01:35 < nathanael> okay, maybe even the other person closed the channel on purpose - maybe forget what i said, but still the last line in the logs i posted seems off
01:36 -!- kon__ [~kon@p200300d4a714b10038bc1e47002358f1.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
01:37 -!- kon__ [~kon@p50882d99.dip0.t-ipconnect.de] has joined #c-lightning
01:41 < cdecker[m]> That's quite alright, we seem to have a knack for correct but alarming log messages :-) We handle each peer in a dedicated subdaemon to isolate them from each other. If the connection gets closed, as was the case here, the process exits and will be restarted when a new connection is established. Dying here refers to the subdaemon exiting, but sounds alarming. We should probably rephrase that to be less alarming :-)
01:43 < _aj_> cdecker[m]: ping re https://github.com/bitcoin/bips/pull/943 ?
01:45 < nathanael> cdecker[m]: thanks for clarifying
01:46 -!- cdecker6 [~cdecker@243.86.254.84.ftth.as8758.net] has joined #c-lightning
01:47 < nathanael> is there an easy way i can test if another node can connect to me? does `telnet ip 9735` achieve that?
01:48 < cdecker[m]> Uh, yeah sorry for the delay aj, ack'd and ready to go 👍
01:49 < cdecker[m]> nathanael: yes, that should work for ipv4 and ipv6
01:49 < nathanael> cdecker[m]: you probably guess the next question, how about torv3?
01:50 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has quit [Ping timeout: 272 seconds]
01:50 -!- cdecker6 is now known as cdecker
02:11 < _aj_> cdecker[m]: \o/
02:13 < _aj_> cdecker[m]: remyer's eltoo sim seems to be 80% of the way to getting basic eltoo+HTLCs working w/ APO; PTLCs and layered commitments (and layered commitments with fees particularly) still a ways away
02:48 < fiatjaf> what are layered commitments, in a nutshell?
02:48 < fiatjaf> I've read your mailing list post a couple of times but I get almost nothing of it, _aj_ 
02:48 < fiatjaf> please help
02:53 < _aj_> fiatjaf: do you know the prolem they solve?
02:53 < _aj_> fiatjaf: (actually, #lightning-dev probably better place for the conversation)
03:45 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
04:15 < nathanael> can i run c-lightning behind tor with my own key for the onion address?
04:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:34 -!- kon__ [~kon@p50882d99.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
04:34 -!- kon__ [~kon@p200300d4a714b10038bc1e47002358f1.dip0.t-ipconnect.de] has joined #c-lightning
04:38 -!- rusty [~rusty@103.93.169.121] has quit [Quit: Leaving.]
04:38 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
04:54 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 258 seconds]
04:55 -!- kon__ [~kon@p200300d4a714b10038bc1e47002358f1.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
04:56 -!- kon__ [~kon@p50882d99.dip0.t-ipconnect.de] has joined #c-lightning
06:21 -!- kon__ [~kon@p50882d99.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
06:22 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has joined #c-lightning
06:29 < nathanael> hmm, had a mutual close going on and were at 60 blocks left and now it says 100 blocks left
06:31 < nathanael> okay and changed back to 62
06:33 < nathanael> ah is that because of a restart from lightningd - maybe
06:33 < nathanael> yes look like
06:42 < nathanael> can someone explain what this means:
06:42 < nathanael> Peer permanent failure in ONCHAIN: Funding transaction spent
06:47 < cdecker[m]> Peer spent the funding output, we can't continue using the channel, need to wait for it to resolve :-)
07:02 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
07:03 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has joined #c-lightning
07:09 < nathanael> cdecker[m]: hmm, but how could the channel get locked in and then the funding transaction get spent?
07:09 < nathanael> isn't the locking tx the funding transaction?
07:10 < cdecker[m]> lockin just means that the funding transaction has reached 1 or 2 confirmations, a collaborative or unilateral close will then spend that funding output triggering us to switch over into the onchain state. So in this case my guess is your peer just decided to close
07:11 < nathanael> ah right thx
07:11 < nathanael> sorry was a stupid question - i need some sleep
07:16 < cdecker[m]> No worries :-)
07:33 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
07:33 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has joined #c-lightning
07:54 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
07:54 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has joined #c-lightning
07:55 < nathanael> ah and i tested with netcat if my node is reachable over tor, at least i hope that is what it means
07:55 < nathanael> like `nc -v -X5 -x localhost:9050 longtorstring.onion 9735`
07:56 < nathanael> from my local machine running tor socks5 on port 9050
07:56 < nathanael> and it succeeds
07:56 < nathanael> so no idea why the other person seams to have problems connecting to my node
07:56 < nathanael> ah node which only runs behind tor is not able to connect to a node which only runs on clearnet? or ist that wrong
07:57 < nathanael> (at least not direclty?!=
08:05 < DeanGuss> correct, the other person needs to be running (and going through) tor to reach a .onion
08:05 < nathanael> thx DeanGuss 
08:15 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
08:15 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has joined #c-lightning
08:29 < nathanael> is someone in the position to try to `lightning-cli connect 025b5150c66f3ea41367829f6e4639c772fe4c7939b71933802233493e6e972a8e` please?
08:36 -!- kon__ [~kon@p200300d4a723ba0039039b9d754dc8c2.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]
08:37 -!- kon__ [~kon@p50882086.dip0.t-ipconnect.de] has joined #c-lightning
08:54 < cdecker[m]> Connected perfectly fine, you're reachable 🙂
09:22 < nathanael> cdecker[m]: awesome thanks - did you connect from clearnet? now it could still be i am not reachable via tor right?
09:22 < nathanael> (haha i don't try to dox you ;))
09:22 < cdecker[m]> True, I was connecting over clearnet
09:23 < nathanael> ok, if some kind soul behind tor reads this, would be lovely if a connection from there could be made, i would sleep a lot better tonight ;)
13:46 -!- nathanael [~nathanael@user/nathanael] has quit [Excess Flood]
13:46 -!- nathanael [~nathanael@user/nathanael] has joined #c-lightning
14:05 -!- valwal [~valwal@96.224.58.144] has quit [Ping timeout: 240 seconds]
14:50 -!- kon__ [~kon@p50882086.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
15:32 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 256 seconds]
16:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:25 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 244 seconds]
16:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:22 -!- reallll [~belcher@user/belcher] has joined #c-lightning
17:25 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
20:04 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning
22:46 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 265 seconds]
23:18 < nathanael> `getinfo` shows 1 pending channel and 3 active channels, but with `listpeers` i only see 3 channels, how can i find out what with this pending channel is going on?
23:26 -!- Shing [~Shing@c-71-197-149-235.hsd1.wa.comcast.net] has joined #c-lightning
23:27 < Shing> hi yall, qq about c-lightning dev: is it similar to bitcoin core dev where I can just start working and put up a PR, or do i need to ask to work on an issue? 
23:36 -!- reallll is now known as belcher
--- Log closed Fri Jul 09 00:00:01 2021