--- Log opened Fri Jan 03 00:00:55 2020
00:11 -!- aqquadro [~name@2001:b07:2ee:6c29:50d3:36e7:3678:8237] has joined #lightning-dev
00:11 -!- aqquadro [~name@2001:b07:2ee:6c29:50d3:36e7:3678:8237] has quit [Changing host]
00:11 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #lightning-dev
00:14 -!- marcoagner [~user@bl11-16-162.dsl.telepac.pt] has joined #lightning-dev
00:15 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev
00:19 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 248 seconds]
00:26 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Ping timeout: 250 seconds]
00:45 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #lightning-dev
01:15 -!- aqquadro [~name@net-37-159-134-26.cust.vodafonedsl.it] has joined #lightning-dev
01:15 -!- aqquadro [~name@net-37-159-134-26.cust.vodafonedsl.it] has quit [Changing host]
01:15 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #lightning-dev
01:40 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
01:41 -!- sh_smith [~sh_smith@cpe-172-88-21-24.socal.res.rr.com] has quit [Ping timeout: 268 seconds]
01:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
01:45 -!- sh_smith [~sh_smith@cpe-172-88-21-24.socal.res.rr.com] has joined #lightning-dev
02:01 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
02:03 -!- phwalkr [~phwalkr@2001:1284:f01c:4df:a887:4b7d:a54:97b8] has joined #lightning-dev
02:08 < phwalkr> Hi there. Would somebody know what kind of issues does Lightning have when running as an SPV node? Any pitfalls?
02:27 -!- phwalkr [~phwalkr@2001:1284:f01c:4df:a887:4b7d:a54:97b8] has quit [Remote host closed the connection]
02:29 -!- phwalkr [~phwalkr@2001:1284:f01c:4df:a887:4b7d:a54:97b8] has joined #lightning-dev
02:34 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
02:38 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Client Quit]
02:40 < phwalkr> And about the routing protocol, is it an onion protocol?
02:49 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
02:52 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev
02:52 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
02:53 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lightning-dev
03:17 -!- diogosergio [~diogoserg@212.36.34.126] has joined #lightning-dev
03:27 -!- diogosergio [~diogoserg@212.36.34.126] has quit [Ping timeout: 260 seconds]
03:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
03:37 -!- diogosergio [~diogoserg@212.36.34.126] has joined #lightning-dev
03:38 < darosior> phwalkr: yep, described here https://github.com/lightningnetwork/lightning-rfc/blob/master/04-onion-routing.md
03:40 < phwalkr> darosior: Thanks for the reference. And what about lightning running as an SPV node, is it possible?
03:40 < darosior> phwalkr: SPV is for Bitcoin wallets/nodes
03:42 < phwalkr> hm, right
03:43 -!- molly [~molly@unaffiliated/molly] has joined #lightning-dev
03:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 258 seconds]
03:45 -!- designwish [~designwis@51.ip-51-68-136.eu] has quit [Quit: ZNC - https://znc.in]
03:46 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has joined #lightning-dev
03:53 -!- designwish [~designwis@51.ip-51-68-136.eu] has joined #lightning-dev
04:00 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Quit: Leaving]
04:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
04:14 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
04:14 -!- phwalkr [~phwalkr@2001:1284:f01c:4df:a887:4b7d:a54:97b8] has quit [Remote host closed the connection]
04:20 -!- AbramAdelmo_ [AbramAdelm@gateway/vpn/protonvpn/abramadelmo] has quit [Read error: Connection reset by peer]
04:21 -!- AbramAdelmo [AbramAdelm@gateway/vpn/protonvpn/abramadelmo] has joined #lightning-dev
04:30 -!- jonatack [~jon@134.19.179.163] has joined #lightning-dev
04:39 -!- diogosergio [~diogoserg@212.36.34.126] has quit [Ping timeout: 258 seconds]
04:42 -!- jonatack [~jon@134.19.179.163] has quit [Ping timeout: 260 seconds]
04:43 -!- jonatack [~jon@134.19.179.163] has joined #lightning-dev
04:59 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Quit: This computer has gone to sleep]
05:01 -!- mauz555 [~mauz555@2a01:e35:8ab1:dea0:b8e4:64b:ef9f:64cb] has joined #lightning-dev
05:14 -!- Jmabsd [~jmabsd@unaffiliated/jmabsd] has joined #lightning-dev
05:14 < Jmabsd> https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md re commitment transaction says "locktime: upper 8 bits are 0x20, lower 24 bits are the lower 24 bits of the obscured commitment number"
05:14 < Jmabsd> that means the commitment transaction will be processed at first at a Unix epoch time like a couple million years into the future ??????? 
05:20 -!- MrPaz [~MrPaz@24.14.251.223] has joined #lightning-dev
05:23 -!- b33rkeg [~b33rkeg@ptr-7svqdlqw6r39dmqmh8z.18120a2.ip6.access.telenet.be] has joined #lightning-dev
05:23 -!- b33rkeg [~b33rkeg@ptr-7svqdlqw6r39dmqmh8z.18120a2.ip6.access.telenet.be] has quit [Client Quit]
05:24 < Jmabsd> ah the sequence number cancels it, er
05:34 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
05:39 -!- mauz555 [~mauz555@2a01:e35:8ab1:dea0:b8e4:64b:ef9f:64cb] has quit [Remote host closed the connection]
05:48 -!- jonatack [~jon@134.19.179.163] has quit [Ping timeout: 268 seconds]
05:50 -!- diogosergio [~diogoserg@212.36.34.126] has joined #lightning-dev
06:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]
06:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
06:14 -!- MrPaz [~MrPaz@24.14.251.223] has quit [Quit: Leaving]
06:24 -!- wullon [~wullon@241.243.86.88.rdns.comcable.net] has quit [Ping timeout: 245 seconds]
06:43 -!- trotski2000_ [uid206086@gateway/web/irccloud.com/x-kyxjgtijkbldajzj] has joined #lightning-dev
06:58 -!- Jmabsd2 [~jmabsd@14-0-170-130.static.pccw-hkt.com] has joined #lightning-dev
07:02 -!- Jmabsd [~jmabsd@unaffiliated/jmabsd] has quit [Ping timeout: 265 seconds]
07:05 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
07:07 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has joined #lightning-dev
07:20 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #lightning-dev
07:27 -!- Jmabsd2 [~jmabsd@14-0-170-130.static.pccw-hkt.com] has quit [Read error: Connection reset by peer]
07:36 -!- diogosergio [~diogoserg@212.36.34.126] has quit [Ping timeout: 268 seconds]
07:44 -!- Jmabsd [~jmabsd@14-0-170-130.static.pccw-hkt.com] has joined #lightning-dev
07:46 -!- Jmabsd [~jmabsd@14-0-170-130.static.pccw-hkt.com] has quit [Read error: Connection reset by peer]
07:49 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev
07:52 -!- diogosergio [~diogoserg@212.36.34.126] has joined #lightning-dev
07:52 -!- mol [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
07:56 -!- Jmabsd [~jmabsd@14-0-170-130.static.pccw-hkt.com] has joined #lightning-dev
08:03 -!- Jmabsd [~jmabsd@14-0-170-130.static.pccw-hkt.com] has quit [Read error: Connection reset by peer]
08:15 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Quit: This computer has gone to sleep]
08:22 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
08:39 -!- diogosergio [~diogoserg@212.36.34.126] has quit [Ping timeout: 265 seconds]
09:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
09:13 -!- SirRichard [~SirRichar@cblmdm72-240-113-19.buckeyecom.net] has quit [Quit: SirRichard]
09:19 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds]
09:46 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
10:17 -!- pepesza [~pepesza@185.83.218.228] has joined #lightning-dev
10:20 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 265 seconds]
10:23 -!- mol [~molly@unaffiliated/molly] has joined #lightning-dev
10:47 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #lightning-dev
10:50 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 260 seconds]
11:10 -!- diogosergio [~diogoserg@172.98.93.212] has joined #lightning-dev
11:17 -!- trotski2000_ [uid206086@gateway/web/irccloud.com/x-kyxjgtijkbldajzj] has quit [Quit: Connection closed for inactivity]
11:22 -!- aqquadro [~name@2001:b07:2ee:6c29:50d3:36e7:3678:8237] has joined #lightning-dev
11:22 -!- aqquadro [~name@2001:b07:2ee:6c29:50d3:36e7:3678:8237] has quit [Changing host]
11:22 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #lightning-dev
11:43 -!- laurentmt [~Thunderbi@92.223.89.146] has joined #lightning-dev
11:44 -!- laurentmt [~Thunderbi@92.223.89.146] has quit [Client Quit]
12:10 -!- AbramAdelmo [AbramAdelm@gateway/vpn/protonvpn/abramadelmo] has quit [Ping timeout: 240 seconds]
12:36 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has joined #lightning-dev
12:45 -!- tryphe_ is now known as tryphe
13:37 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #lightning-dev
13:40 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
13:48 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Quit: This computer has gone to sleep]
13:51 -!- arshbo3000 [~arshbot@99-23-136-47.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 260 seconds]
13:52 -!- arshbot [~arshbot@99-23-136-47.lightspeed.tukrga.sbcglobal.net] has joined #lightning-dev
13:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds]
14:09 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
14:14 -!- diogosergio [~diogoserg@172.98.93.212] has quit [Ping timeout: 268 seconds]
14:26 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Quit: This computer has gone to sleep]
14:32 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
14:46 -!- nobody123 [~nobody123@185.106.102.241] has quit [Remote host closed the connection]
14:46 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
14:46 -!- nobody123 [~nobody123@185.106.102.241] has quit [Remote host closed the connection]
14:47 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
14:48 -!- nobody123 [~nobody123@185.106.102.241] has quit [Read error: Connection reset by peer]
14:49 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
14:53 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Remote host closed the connection]
14:53 -!- nobody123 [~nobody123@185.106.102.241] has quit [Ping timeout: 258 seconds]
15:11 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
15:11 < fiatjaf> if two nodes with dynamic IPs open a channel between themselves, is that going to cause bad outcomes?
15:12 < fiatjaf> like then the IP of them change they won't be able connect again forever?
15:12 < fiatjaf> or are the new IPs going to propagate through gossip and the peers will be able to discover them through other peers and reconnect?
15:12 < fiatjaf> (if yes, then does that only work if both peers have other channels besides the channel with each other? or will the gossip be sent through random peers with which they don't have channels?)
16:08 < weex> fiatjaf: instead of ip, dynamic dns would be good to use if you're on dynamic ip
16:08 < weex> dynamic ips can be pretty stable but working dynamic dns removes the problem of ips changing
16:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 265 seconds]
16:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
16:50 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
16:54 -!- nobody123 [~nobody123@185.106.102.241] has quit [Ping timeout: 265 seconds]
17:01 -!- mauz555 [~mauz555@2a01:e35:8ab1:dea0:b8e4:64b:ef9f:64cb] has joined #lightning-dev
17:05 < ghost43> weex: sure but you cannot put a domain name in a node announcement
17:05 < ghost43> only raw ip or tor hidden service
17:05 -!- molly [~molly@unaffiliated/molly] has joined #lightning-dev
17:05 -!- marcoagner [~user@bl11-16-162.dsl.telepac.pt] has quit [Ping timeout: 268 seconds]
17:05 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has joined #lightning-dev
17:06 -!- mauz555 [~mauz555@2a01:e35:8ab1:dea0:b8e4:64b:ef9f:64cb] has quit []
17:06 < ghost43> fiatjaf: they should be able to find each other again through updated node announcements in the gossip as you suggested
17:08 < fiatjaf> ghost43: even if one of them only has that single channel?
17:08 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 268 seconds]
17:09 < ghost43> fiatjaf: why would that matter?
17:09 < ghost43> IIRC node announcements are supposed to be propagated onwards if there is at least one corresponding channel announcement for that node id
17:10 < ghost43> "if node_id is NOT previously known from a channel_announcement message, OR if timestamp is NOT greater than the last-received node_announcement from this node_id: SHOULD ignore the message"
17:11 < ghost43> this seems to be the only non-trivial requirement
17:11 < fiatjaf> ghost43: because I have the impression that nodes only send their gossip to other nodes with which they have channels
17:12 < ghost43> what exactly mean by "send their gossip"?
17:12 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev
17:12 < fiatjaf> ghost43: so according to what you say node_announcement messages that just update the ip address should be ignored? I think they aren't being ignored today, at least not by everyone. 
17:12 < fiatjaf> ghost43: I mean "send their node_annoucements"
17:13 < fiatjaf> nodeA is connected to nodeB because they have a channel, so nodeA sends its node_annoucement and other stuff to nodeB.
17:13 < ghost43> no I did not mean they should be ignored in your scenario. on the contrary, I am arguing if there is a pre-existing channel, they should be accepted and propagated
17:13 < fiatjaf> if nodeA is not connected to anyone what happens?
17:14 < fiatjaf> oh, right, sorry, I misread it
17:14 < fiatjaf> (about the spec quote)
17:16 < ghost43> nodes typically maintain multiple transport level connections to other nodes. maintaining 4 connections is I believe was at some point suggested in one of the BOLTs though I cannot find it now
17:18 < ghost43> you can use these connections to "broadcast" your node announcement
17:27 < fiatjaf> oh, right
17:27 < fiatjaf> that solves it, then
17:27 < fiatjaf> thank you
17:39 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds]
17:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
18:26 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev
18:50 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
18:55 -!- nobody123 [~nobody123@185.106.102.241] has quit [Ping timeout: 240 seconds]
19:03 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Read error: Connection reset by peer]
19:03 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has joined #lightning-dev
19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
19:38 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 268 seconds]
19:38 -!- fiatjaf1 [~fiatjaf@2804:7f2:2996:5492:ea40:f2ff:fe85:d2dc] has joined #lightning-dev
19:41 -!- fiatjaf [~fiatjaf@186.213.100.35] has quit [Ping timeout: 240 seconds]
20:28 -!- captjakk [~captjakk@75-166-188-3.hlrn.qwest.net] has joined #lightning-dev
20:51 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
20:54 -!- nobody123 [~nobody123@185.106.102.241] has quit [Read error: Connection reset by peer]
21:01 -!- captjakk [~captjakk@75-166-188-3.hlrn.qwest.net] has quit [Remote host closed the connection]
21:12 -!- molz_ [~molly@unaffiliated/molly] has joined #lightning-dev
21:15 -!- molly [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
21:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
21:21 -!- zerogue [~irc@nullstruct.com] has quit [Quit: Goodbye Cruel World]
21:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
21:24 -!- zerogue [~irc@nullstruct.com] has joined #lightning-dev
21:40 -!- Relis [~Relis@cpc96290-lewi18-2-0-cust910.2-4.cable.virginm.net] has quit [Quit: This computer has gone to sleep]
21:50 -!- zerogue [~irc@nullstruct.com] has quit [Quit: Goodbye Cruel World]
21:53 -!- zerogue [~irc@nullstruct.com] has joined #lightning-dev
22:00 -!- zerogue [~irc@nullstruct.com] has quit [Quit: Goodbye Cruel World]
22:02 -!- zerogue [~irc@nullstruct.com] has joined #lightning-dev
22:09 -!- zerogue [~irc@nullstruct.com] has quit [Quit: Goodbye Cruel World]
22:11 -!- zerogue [~irc@nullstruct.com] has joined #lightning-dev
22:50 -!- zerogue [~irc@nullstruct.com] has quit [Quit: Goodbye Cruel World]
22:52 -!- zerogue [~irc@nullstruct.com] has joined #lightning-dev
22:52 -!- nobody123 [~nobody123@185.106.102.241] has joined #lightning-dev
22:54 -!- nobody123 [~nobody123@185.106.102.241] has quit [Read error: Connection reset by peer]
23:29 -!- Guest59899 [~quassel@223.177.233.220.static.exetel.com.au] has quit [Ping timeout: 240 seconds]
--- Log closed Sat Jan 04 00:00:56 2020