--- Log opened Fri Mar 26 00:00:07 2021
00:03 -!- tigermousr [~tigermous@unaffiliated/tigermousr] has quit [Quit: %empty%]
00:05 -!- klaiko [d5bdb9c6@host-213-189-185-198.dynamic.voo.be] has joined #c-lightning
00:08 < klaiko> Hello community, I am new to this channel and happy to be able to participate in the lightning network.
00:12 < klaiko> I am using FreeBSD 12.2 and would like to know what is best for deploying lightning. I saw that there are several choices to deploy it, there is the Bitcoind + c-lightning deamond but also there is lnd on Github. In your experience, which one is best to use?
01:11 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
01:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
02:12 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning
03:27 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has joined #c-lightning
03:33 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning
04:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
04:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
05:48 <@niftynei> klaiko: this channel is mostly c-lightning users, so unfortunately most of us don't have experience with lnd
05:49 <@niftynei> i'd highly recommend c-lightning, but i'm definitely biased :)
06:52 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal]
06:55 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has joined #c-lightning
07:31 -!- jonatack__ [~jon@37.165.100.95] has joined #c-lightning
07:49 < grubles> what is failcode 4103 
07:52 < grubles> 'failcodename': 'WIRE_TEMPORARY_CHANNEL_FAILURE'   <-- seems to be this?
07:59 -!- jonatack [~jon@37.173.70.220] has joined #c-lightning
08:01 -!- jonatack__ [~jon@37.165.100.95] has quit [Ping timeout: 240 seconds]
08:12 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
08:32 -!- snyke is now known as cdecker
08:45 -!- ksedgwic [~ksedgwic@192-184-130-48.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal]
08:58 -!- jonatack [~jon@37.173.70.220] has quit [Read error: Connection reset by peer]
08:59 -!- jonatack [~jon@37.173.70.220] has joined #c-lightning
09:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
09:27 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
09:47 -!- belcher_ is now known as belcher
10:09 -!- jonatack [~jon@37.173.70.220] has quit [Ping timeout: 240 seconds]
10:47 < fiatjaf> grubles: could be different things but most likely it's lack of balance in that channel
10:48 < fiatjaf> klaiko: the best is c-lightning
11:20 -!- fiatjaf [~fiatjaf@2804:7f2:2a8c:f814:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 258 seconds]
11:28 -!- fiatjaf [~fiatjaf@2804:7f2:2a8c:f814:ea40:f2ff:fe85:d2dc] has joined #c-lightning
11:53 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
12:12 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 260 seconds]
12:15 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
12:34 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 246 seconds]
12:36 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
12:38 -!- jonatack [~jon@88.124.242.136] has quit [Excess Flood]
12:39 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
12:44 -!- klaiko [d5bdb9c6@host-213-189-185-198.dynamic.voo.be] has quit [Quit: Connection closed]
13:30 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 265 seconds]
13:32 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
13:55 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has quit [Quit: Leaving]
14:11 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has joined #c-lightning
14:13 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds]
14:14 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
14:41 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
14:42 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
14:45 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds]
14:49 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
15:07 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Quit: jonatack]
15:19 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #c-lightning
16:04 <@niftynei> rusty/cdecker: is it reasonable to suspect that an RPC call's return and a notification firing might happen out of order? 
16:04 <@niftynei> https://github.com/ElementsProject/lightning/issues/4455#issuecomment-808560787
16:05 <@niftynei> dualopend is a single process, so the messages from the peer should be read in order (and the logs confirm that they were)
16:05 <@niftynei> they're then relayed to lightningd (presumably in order?) who then relays/forwards them to the plugin daemon
16:07 <@niftynei> of the messages is a reply to an RPC; the other's a notification. but that shouldn't really matter, they're both JSON messages. (the only difference between them would be that the RPC reply contains an ID)
16:08 <@niftynei> the code, as is, expects a race in one of the pathways but not the other (which is the one that had the assert fail)
17:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has left #c-lightning []
17:48 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-uyoebgucxhmqymle] has joined #c-lightning
18:05 -!- vincenzopalazzo [~vincenzop@host-95-249-217-78.retail.telecomitalia.it] has quit [Quit: Leaving]
19:00 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
19:08 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
20:08 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:19 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
20:20 < warren> Anyone have signet LN nodes? I'm looking for peers.
20:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds]
20:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
20:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
23:24 -!- _rny [~rny@gateway/tor-sasl/renlord] has joined #c-lightning
23:26 -!- rny [~rny@gateway/tor-sasl/renlord] has quit [Remote host closed the connection]
23:32 -!- klaiko [d5bdb9c6@host-213-189-185-198.dynamic.voo.be] has joined #c-lightning
23:37 -!- tigermousr [~tigermous@unaffiliated/tigermousr] has joined #c-lightning
23:52 -!- _rny is now known as rny
--- Log closed Sat Mar 27 00:00:08 2021