--- Log opened Wed Sep 01 00:00:54 2021
00:52 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds]
03:46 -!- Victorsueca [~Victorsue@90.165.120.190] has quit [Ping timeout: 248 seconds]
05:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:22 < mschmoock> cdecker[m]: self-ACKED and merged https://github.com/lightningd/plugins/pull/284 nobody insisted on furhter changes :D
05:43 < jasan> michaelfolkson: not too reckless to run a testnet and signet c-lightning nodes on the same machine (doing that for a year now) see https://ln.bublina.eu.org
06:44 < cdecker[m]> michaelfolkson: it's perfectly fine to run any number of nodes for any combination of networks as long as you keep home-directories (`--lightning-dir`) and `--bind-addr` / `--addr` bindings distinct. For different networks we already have subdirectories, so no need to specify those manually. But multiple nodes for the same network would conflict on the pid file and back out safely.
06:45 < cdecker[m]> mschmoock: thanks for the merge ^^
06:59 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has joined #c-lightning
07:02 < michaelfolkson> Thanks cdecker jasan. Added a draft answer to this https://bitcoin.stackexchange.com/questions/108431/should-you-be-able-to-run-a-mainnet-c-lightning-node-in-parallel-with-a-signet-c/
07:07 < cdecker[m]> Excellent, was about to write one myself, going a bit more into detail. Maybe I'll do that once I am back on a real keyboard
07:12 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has quit [Ping timeout: 252 seconds]
07:12 -!- jarthur_ [~jarthur@2603-8080-1540-002d-f53f-9536-c646-bcb2.res6.spectrum.com] has joined #c-lightning
07:13 < michaelfolkson> cdecker[m]: Alternative answers are certainly most welcome :)
07:16 < michaelfolkson> I'll delete "mine" if it doesn't add anything
07:54 < openoms[m]> <michaelfolkson> "Thanks cdecker jasan. Added a..." <- See this screenshot showing 5 nodes parallel https://twitter.com/openoms/status/1397187128136802326
07:54 < openoms[m]> For LND need to carefully specify the ZMQ ports to not mix the blockhashes of the networks
08:03 < openoms[m]> commenting on the question now
08:06 < michaelfolkson> openoms: Awesome, thanks. Added links to the answer
08:14 < openoms[m]> cool, added some details too. Would have commented to your answer, but need a few more upvotes for that. 
08:14 < openoms[m]> thanks for linking the question, it makes me excited since I was paying with this a lot in the past months
08:24 < michaelfolkson> Nah an alternative answer is better than a comment anyway :)
09:34 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
10:05 -!- jarthur_ [~jarthur@2603-8080-1540-002d-f53f-9536-c646-bcb2.res6.spectrum.com] has quit [Ping timeout: 240 seconds]
10:09 -!- jarthur [~jarthur@2603-8080-1540-002d-b495-e64a-b23b-4c53.res6.spectrum.com] has joined #c-lightning
11:28 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
11:34 -!- Klabo [~Klabo@c-73-170-190-23.hsd1.ca.comcast.net] has quit [Quit: Client closed]
11:59 < michaelfolkson> A question in the comments that hasn't got answered yet (and I'm stuck on too) https://bitcoin.stackexchange.com/questions/88305/why-doesnt-lightning-have-dns-bootstrapping/
12:00 < michaelfolkson> The last thing I don't quite understand is how to specify the DNS query to get a testnet node. BOLT10 says that the "realm byte" r is "used to specify what realm the returned nodes must support" with the default value of "0 (Bitcoin)", but it doesn't mention the values for other networks...
12:21 < michaelfolkson> Presumably the normal user behavior is to open a channel to a specific peer and get the topology gossip from them (worst they can do is give you rubbish and cause your attempted payments to fail which is not in their interests with routing fees)
12:32 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
13:26 -!- valwal [~valwal@96.224.58.144] has quit [Ping timeout: 240 seconds]
13:31 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
13:48 -!- valwal [~valwal@96.224.58.144] has joined #c-lightning
14:06 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
14:13 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
14:59 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 240 seconds]
15:59 -!- Klabo [~Klabo@c-73-170-190-23.hsd1.ca.comcast.net] has joined #c-lightning
17:18 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
17:30 -!- belcher [~belcher@user/belcher] has joined #c-lightning
17:41 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning
18:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
18:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:37 < ufotofu> can someone try connecting to my node? 03a465772d45616bf6c8450a69191db8f3cf8cca19ff92138735fd5f1d436fe4dc@140.82.21.181
18:45 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
20:07 -!- jarthur [~jarthur@2603-8080-1540-002d-b495-e64a-b23b-4c53.res6.spectrum.com] has quit [Ping timeout: 252 seconds]
20:11 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has joined #c-lightning
21:40 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has quit [Quit: jarthur]
21:55 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has joined #c-lightning
22:27 < nathanael> ufotofu: can't connect
22:40 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 252 seconds]
22:52 -!- jarthur [~jarthur@2603-8080-1540-002d-347a-2581-fcf8-c1f7.res6.spectrum.com] has quit [Quit: jarthur]
--- Log closed Thu Sep 02 00:00:56 2021