--- Day changed Thu Aug 31 2017 00:01 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has joined #lnd 00:32 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 00:47 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 00:47 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 00:48 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 00:48 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 01:22 -!- JackH [~laptop@46.231.18.66] has joined #lnd 01:37 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 01:38 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 01:56 -!- JackH [~laptop@46.231.18.66] has quit [Ping timeout: 240 seconds] 02:00 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has quit [Ping timeout: 260 seconds] 02:34 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Read error: Connection reset by peer] 02:35 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 02:40 -!- mnkk [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 02:40 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Read error: Connection reset by peer] 02:44 -!- dakk [~dakk@dynamic-adsl-78-15-219-146.clienti.tiscali.it] has joined #lnd 03:07 -!- JackH [~laptop@46.231.18.66] has joined #lnd 03:16 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 03:51 < cdecker> roasbeef, and I'm pretty sure we are using the hash in the same direction that bitcoin-cli spits it out 03:51 < cdecker> This is the relevant logline: DEBUG:root:lightningd: lightningd_opening(26873): TRACE: sync_crypto_write: 00200f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e22068deb76f2d9fb1e61656fd7f661c4db0f247eec093a40840fd34c1e7048ce4cb6000000000098968000000000000000000000000000000222ffffffffffffffff00000000000186a0000000000000000000003a98000601e3033848482454ef6fd3fc26274446f8b2149025b0ee840598d83911603ce1b2854102c97f01005480538258ff93394368da39894e764a734 03:51 < cdecker> 5ae199b446621539667d803d30947f6483e881ee7ea6bef64ed730cd3d783ab1fd24571a74791a8560b4a910255a30aef0aabe30b9779a3ac2da31c03c49d5dbc4ea2142502570e48555585cc033ecc5069bed76d7814bd83509e94cdda956d13ba5f642df129081ed761df42b901 03:52 < cdecker> Bytes 3 to 35 correspond exactly to the output of bitcoin-cli -regtest getblockhash 0 (0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206) 04:26 -!- sh_smith [foobar@cpe-76-174-26-91.socal.res.rr.com] has quit [Ping timeout: 246 seconds] 04:28 -!- sh_smith [foobar@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 04:46 -!- deusexbeer [~deusexbee@093-092-176-207-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 260 seconds] 04:46 -!- deusexbeer [~deusexbee@093-092-181-012-dynamic-pool-adsl.wbt.ru] has joined #lnd 05:53 -!- [a]akselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has joined #lnd 05:54 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has quit [Disconnected by services] 05:54 -!- [a]akselrod is now known as aakselrod 06:05 -!- MaxSan [~one@185.156.175.35] has quit [Ping timeout: 240 seconds] 06:08 -!- MaxSan [~one@185.156.175.35] has joined #lnd 06:08 -!- MaxSan [~one@185.156.175.35] has quit [Max SendQ exceeded] 06:10 -!- MaxSan [~one@185.156.175.35] has joined #lnd 06:10 -!- MaxSan [~one@185.156.175.35] has quit [Max SendQ exceeded] 06:37 -!- deusexbeer [~deusexbee@093-092-181-012-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 240 seconds] 06:39 -!- deusexbeer [~deusexbee@080-250-075-224-dynamic-pool-adsl.wbt.ru] has joined #lnd 06:45 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has quit [Ping timeout: 255 seconds] 07:04 -!- MaxSan [~one@185.156.175.35] has joined #lnd 07:39 -!- esotericnonsense [~esoteric@gateway/vpn/privateinternetaccess/esotericnonsense] has quit [Ping timeout: 260 seconds] 07:40 -!- esotericnonsense [~esoteric@gateway/vpn/privateinternetaccess/esotericnonsense] has joined #lnd 07:58 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has joined #lnd 08:19 -!- kermie [57d51619@gateway/web/freenode/ip.87.213.22.25] has quit [Ping timeout: 260 seconds] 09:02 -!- MaxSan [~one@185.156.175.35] has quit [Quit: Leaving.] 09:10 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 09:24 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 10:02 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has joined #lnd 10:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 10:23 <@roasbeef> cdecker: sure but iirc it follows the bitcoin custom of reversing the hash before printing it out, so on the wire it should have the opposite byte order 10:24 <@roasbeef> cdecker: https://github.com/btcsuite/btcd/blob/master/chaincfg/genesis.go#L90 10:26 < cdecker> I know, but you seem to accept this format in the gossip messages (channel_announce also has a chain_hash) 10:27 < cdecker> We just need to agree on which direction to go, and I believe that being consistent with bitcoin will cause less confusion in the long run 10:28 <@roasbeef> there's currently no verification of the chain_hash within our gossip message handling 10:28 <@roasbeef> yes i think we're consistent with that, bitcoin-cli reverses before printing 10:28 <@roasbeef> the true order is in what I linked above 10:28 <@roasbeef> compare those other genesis hash definitions with how bitcoin-cli prints them out, they're consistent 10:29 <@roasbeef> that code uses chainhash.Hash, whos' String() method reverses the byte order before printing 10:34 -!- deusexbeer [~deusexbee@080-250-075-224-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 240 seconds] 10:35 -!- deusexbeer [~deusexbee@095-129-175-226-dynamic-pool-adsl.wbt.ru] has joined #lnd 10:47 -!- JackH [~laptop@46.231.18.66] has quit [Ping timeout: 240 seconds] 10:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 255 seconds] 10:52 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 11:00 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 11:02 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 11:03 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 11:09 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 11:09 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 11:09 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 11:10 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 11:17 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 11:47 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 12:00 -!- MaxSan [~one@185.156.175.43] has joined #lnd 12:16 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 12:42 -!- mnkk [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Ping timeout: 252 seconds] 12:46 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 13:12 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds] 13:18 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 13:18 -!- mnkk [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 13:31 -!- dermoth_ [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 13:31 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Disconnected by services] 13:31 -!- dermoth_ is now known as dermoth 14:40 -!- light1 [5b6c1c05@gateway/web/freenode/ip.91.108.28.5] has joined #lnd 14:40 < light1> how LN will naturally appear and grow? who will be the first paying and for what? 14:40 < cdecker> Whatever, reversing the hash is no biggy for either implementation 14:40 < light1> have you plotted the scenario how will it be growing? 14:40 < cdecker> However I'm still not able to open a channel with lnd: DEBUG:root:lnd: 2017-08-31 23:34:49.487 [ERR] FNDG: Unable to initialize reservation: -5: Invalid address or key: tb1qa8qw324ea34huj8scaduhn69g4uy0qefafxutp 14:41 < cdecker> This happens in either direction (c-lightning opening to lnd, and lnd opening to c-lightning) 14:48 <@roasbeef> cdecker: you'll need to update the btcd node running, as recently switched over to bech32 14:48 <@roasbeef> from the roasbeef/btcd fork 14:48 < cdecker> Ah k 14:49 < cdecker> btcsuite/btcd @ master should work? 14:52 <@roasbeef> roasbeef/btcd @ master 14:57 <@roasbeef> aight two queries it is 14:58 <@roasbeef> modifying your seeder to use our RPC system, can switch it over to just connect to the network once we split out the peer logic into it's own package 15:01 -!- light1 [5b6c1c05@gateway/web/freenode/ip.91.108.28.5] has quit [Quit: Page closed] 15:06 < cdecker> Don't look too close at the code, will need to clean up and document a lot more ^^ 15:07 <@roasbeef> hehe :p 15:07 <@roasbeef> about to test out my forked version 15:07 <@roasbeef> spotted one area I think ds.rootDomain wasn't being should directly, but should be 16:07 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 252 seconds] 16:15 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 16:16 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Max SendQ exceeded] 16:17 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 16:17 < molz> oh cool .. so we can get a bech32 address from btcd? 16:18 < molz> roasbeef, is this your address sent from btcd here: https://btc.com/a4bc261faf9ca47722760c9f9f075ab974c7351d8da7b0b5e5a316b3aa7aefa2 16:20 < molz> roasbeef, btcd goes too slow on mainnet 16:20 < molz> it needs some grease ... :P 16:25 -!- Deadhand [~deadhand@2607:fea8:e380:10f::3] has quit [Ping timeout: 258 seconds] 16:30 -!- Deadhand [~deadhand@2607:fea8:e380:10f::7] has joined #lnd 16:59 -!- abpa [~abpa@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 17:05 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:06 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:06 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:07 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:08 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Read error: Connection timed out] 17:09 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 17:09 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Max SendQ exceeded] 17:10 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 17:12 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 17:13 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Max SendQ exceeded] 17:13 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 17:13 -!- dabura667 [~dabura667@KD111103034253.ppp-bb.dion.ne.jp] has joined #lnd 17:13 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 246 seconds] 17:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:17 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:17 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Max SendQ exceeded] 17:18 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 17:18 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 17:21 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 17:22 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 246 seconds] 17:46 -!- dabura667 [~dabura667@KD111103034253.ppp-bb.dion.ne.jp] has quit [Remote host closed the connection] 18:20 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 18:28 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 18:43 <@roasbeef> yeee have DNS discovery working off the seeder now cdecker, now to figure out my own name server situation... 19:18 <@roasbeef> and we haz dns!!! 19:18 <@roasbeef> $ dig nodes.lightning.directory SRV 19:18 <@roasbeef> $ dig nodes.lightning.directory 19:20 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 19:24 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 246 seconds] 19:38 -!- dabura667 [~dabura667@KD182251112124.au-net.ne.jp] has joined #lnd 19:40 -!- dabura667 [~dabura667@KD182251112124.au-net.ne.jp] has quit [Client Quit] 19:44 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 20:11 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 20:12 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 255 seconds] 20:14 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 20:57 -!- MaxSan [~one@185.156.175.43] has quit [Quit: Leaving.] 21:51 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 252 seconds] 21:56 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer] 21:59 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #lnd 22:32 -!- dakk [~dakk@dynamic-adsl-78-15-219-146.clienti.tiscali.it] has quit [Ping timeout: 252 seconds] 22:47 -!- Deadhand [~deadhand@2607:fea8:e380:10f::7] has quit [Ping timeout: 252 seconds] 22:50 -!- Deadhand [~deadhand@2607:fea8:e380:10f::7] has joined #lnd 23:04 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 23:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 268 seconds] 23:47 -!- mnkk [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 23:49 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 23:49 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 23:56 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 255 seconds]