--- Day changed Mon Jun 04 2018 00:30 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 00:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 00:48 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 00:51 -githubby:#c-lightning- [lightning] arowser opened pull request #1539: udpate broken link in deployable-lightning.lyx (master...link) https://git.io/vhlH9 01:08 -!- stranger64 [~stranger6@69.146.4.47] has quit [Ping timeout: 245 seconds] 01:09 -!- stranger64 [~stranger6@69.146.4.47] has joined #c-lightning 01:56 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 01:57 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 02:29 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:06 < rusty> sturles: it means they asked the channel delay to be 1201 blocks (!), and we only permitted 720. 03:07 < sturles> OK. Some other popular Lightning implementation defaults to 1201, perhaps? 03:11 <@cdecker> Yes, lnd is asks for that, and it means that your funds will be unavailable for a 1w+ if they disappear 03:11 <@cdecker> We're trying to get them to see the light :-) 03:15 -!- sturles_ [~sturles@ulrik.uio.no] has joined #c-lightning 03:15 -!- sturles_ [~sturles@ulrik.uio.no] has quit [Changing host] 03:15 -!- sturles_ [~sturles@unaffiliated/sturles] has joined #c-lightning 03:17 -!- sturles [~sturles@unaffiliated/sturles] has quit [Killed (rajaniemi.freenode.net (Nickname regained by services))] 03:17 -!- sturles_ is now known as sturles 03:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 04:22 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 04:56 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 04:59 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 05:29 -!- tiagotrs [~user@p5DC46C4C.dip0.t-ipconnect.de] has joined #c-lightning 05:29 -!- tiagotrs [~user@p5DC46C4C.dip0.t-ipconnect.de] has quit [Changing host] 05:29 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 05:36 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 05:45 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 06:26 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 260 seconds] 06:41 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning 07:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 08:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:10 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 08:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:18 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:27 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 10:01 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning 10:01 -!- amp__ [~amp@24.136.5.183] has quit [Remote host closed the connection] 10:02 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning 10:04 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 256 seconds] 11:19 < molz> sturles, i think if you lower the funding amount you might be able to pass that 11:20 -!- tiagotrs [~user@p5DC46496.dip0.t-ipconnect.de] has joined #c-lightning 11:20 -!- tiagotrs [~user@p5DC46496.dip0.t-ipconnect.de] has quit [Changing host] 11:20 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 12:17 < roasbeef> sturles: ofc it's a trade off, would you rather wait a bit longer and be safe, or make the times shorter and be out of luck if the power at your home goes out over the weekend? 12:20 < sturles> I'd rather wait a bit longer. 12:53 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Ping timeout: 240 seconds] 12:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:07 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning 13:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 14:09 -!- Lightblock [uid302821@gateway/web/irccloud.com/x-gekrgysiyugundfd] has joined #c-lightning 14:11 < Lightblock> hello 14:11 < Lightblock> it is pleasure to be here 14:12 < Lightblock> I have a very basic question I believe, but as funny as it sounds I struggled to find any substantial info that could help solve it 14:13 < Lightblock> 1) bitcoin node latest version, full-synced, running on mainnet 14:13 < Lightblock> 2) c-lightning implementation of lightning node cloned and built, everything seems fine 14:13 < Lightblock> 3) bitcoin data is located in specific directory 14:13 < Lightblock> 4) whilw trying to set custom bitcoin datadir for lightningd getting this error: "lightningd(6831): Wallet blockchain hash does not match network blockchain hash: 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f != 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 14:13 < Lightblock> lightningd: Wallet network check failed. 14:13 < Lightblock> " 14:13 < Lightblock> 5) while trying to launcch lightningd on mainnet via command lightningd --network=bitcoin 14:13 < Lightblock> getting error: Could not connect to bitcoind using bitcoin-cli. Is bitcoind running? 14:13 < Lightblock> however bitcoind is runing, bitcoin-cli commands are working 14:13 < Lightblock> really lost and could find any substantial information on that anywhere on the net 14:13 -githubby:#c-lightning- [lightning] jsarenik opened pull request #1542: external/Makefile: Simplify build and fix race condition (master...jasan/simplify) https://git.io/vh4U3 14:14 < Lightblock> anyone alive? 14:15 < Lightblock> seems like chainparams are set to testnet, but how to point them on mainnet? 14:33 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 276 seconds] 15:01 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 16:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:04 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 18:19 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 18:20 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 19:35 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 19:36 -!- booyah_ [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 21:13 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 23:28 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 250 seconds]