--- Day changed Thu Apr 19 2018 00:17 < blockstream_bot> [Vegard Engen, Blockstream] Thank you. 00:18 < blockstream_bot> [Vegard Engen, Blockstream] My first question: what can be done by differences in opinion between various implementations in regards to safe fees? I use LND for now, *should* get around to test c-lightning at some point... 00:20 < blockstream_bot> [Vegard Engen, Blockstream] But right now, I have given up trying to connect to c-lightning nodes. 00:20 < blockstream_bot> I am happy with a pointer to a discussion. I am sure this has been debated thoroughly :) 00:45 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 00:45 < blockstream_bot> [Samson Mow, Blockstream] @decker 00:49 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 01:06 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 02:22 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qkcfmuycmrfpsdjc] has joined #c-lightning 02:33 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 02:33 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has joined #c-lightning 02:33 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has quit [Changing host] 02:33 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 02:37 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 03:03 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 248 seconds] 03:11 < blockstream_bot> [Christian Decker, Blockstream] c-lightning is about the only impl that enforces strict fees, which is necessary for safety 03:11 < blockstream_bot> [Christian Decker, Blockstream] There is one issue where lnd was asking for a feerate that'd make the transaction below the relay-fee, and could therefore never be broadcast (if you see 250 vs 253, that's this case) 03:12 < blockstream_bot> [Christian Decker, Blockstream] lnd have signaled that they'll be fixing it soon 03:16 < blockstream_bot> [Vegard Engen, Blockstream] Sure. But I have also seen the same happening with higher fees 03:16 < blockstream_bot> [Vegard Engen, Blockstream] I agree that an implementation should enforce safe limits. Is forceclosing the only thing it can do? 03:24 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Remote host closed the connection] 04:14 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has joined #c-lightning 04:14 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has quit [Changing host] 04:14 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 04:24 -!- CubicEarths [~cubiceart@178.197.231.239] has joined #c-lightning 04:45 -!- CubicEarths [~cubiceart@178.197.231.239] has quit [Remote host closed the connection] 05:19 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-qkcfmuycmrfpsdjc] has quit [Quit: Connection closed for inactivity] 05:58 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 276 seconds] 06:05 -!- dell [d4033968@gateway/web/freenode/ip.212.3.57.104] has joined #c-lightning 06:08 < dell> Hi there! I have a question. I successfully setup lightning on mainnet and setup the connection to blockstreams node - unfortunately I underfunded the payment channel to buy the stickers . I am now trying to close the channel with the command ./cli/lightning-cli close 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 is that correct? MY ssh screen has notupdated for a while will this work? thanks 06:09 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 06:13 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 06:42 < dell> i did control c and now no features work - if i try to start lightning again i get - ./lightningd/lightningd --network bitcoin db_commit_transaction:database is locked:COMMIT;:database is locked 06:51 -!- CubicEarths [~cubiceart@178.197.231.116] has joined #c-lightning 06:54 -!- CubicEarths [~cubiceart@178.197.231.116] has quit [Remote host closed the connection] 06:55 -!- dougsland [douglas@nat/redhat/x-vnwqtxvothtiowox] has joined #c-lightning 07:13 < blockstream_bot> [Robert Olsson, Blockstream] i don’t like forceclosing either. at least give it some time. my btcd derailed a bit. i restarted it without pausing lnd. i usually stop lnd first :) … but this time i was brave… anyhows i started up btcd again, something went fubar with fee estimation, and i got 92 channels instantly closed by c-lightning nodes. miners applauded my bravery. 07:15 < dell> Hi Robert, were you responding to my question? 07:17 < mlz> dell, no i don't think so, i think he was responding to Vegard 07:17 < dell> ok thanks 07:18 < dell> just joined the chat.. 07:18 < mlz> not sure what happened to your node? 07:19 < dell> ye nothing is working now when I ran ./cli/lightning-cli close 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 07:19 < dell> db_commit_transaction:database is locked:COMMIT;:database is locked 07:20 < mlz> dell, i think you might get a quicker response if you post on github issues 07:20 < dell> ok thanks will do... 07:20 < mlz> and get the log 07:20 < mlz> look at in the log to see what you can find 07:21 < dell> how can i get the log - sorry... 07:22 < mlz> there should be a "crash.log" in .lightning directory 07:22 < dell> great thanks 07:24 -!- dell [d4033968@gateway/web/freenode/ip.212.3.57.104] has quit [Quit: Page closed] 07:38 -!- douglas_ [douglas@nat/redhat/x-bfxagclzijjrnbjj] has joined #c-lightning 07:40 -!- dougsland [douglas@nat/redhat/x-vnwqtxvothtiowox] has quit [Ping timeout: 260 seconds] 07:43 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 07:44 < blockstream_bot> [Robert Olsson, Blockstream] oh cool. the irc gateway makes it look like i’m a blockstream employee. can i get my salary over lightning please? 07:49 < zib> you people are weird 07:51 -!- grafcaps [~haroldbr@50.90.26.145] has joined #c-lightning 08:00 -!- grafcaps [~haroldbr@50.90.26.145] has quit [Ping timeout: 264 seconds] 08:14 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 08:28 -!- shesek [~shesek@bzq-84-110-56-13.cablep.bezeqint.net] has joined #c-lightning 08:28 -!- shesek [~shesek@bzq-84-110-56-13.cablep.bezeqint.net] has quit [Changing host] 08:28 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 09:02 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:02 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 09:11 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 11:51 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 248 seconds] 11:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-dsrapxzkvwkukgnf] has joined #c-lightning 12:40 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has joined #c-lightning 12:40 -!- tiagotrs [~user@p5DC462DB.dip0.t-ipconnect.de] has quit [Changing host] 12:40 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 14:00 -!- freannrak [~ar@188.166.55.44] has quit [Ping timeout: 264 seconds] 14:03 -!- douglas_ [douglas@nat/redhat/x-bfxagclzijjrnbjj] has quit [Ping timeout: 256 seconds] 14:35 -!- dongcarl [~dongcarl@c-24-5-70-69.hsd1.ca.comcast.net] has quit [Quit: ZNC 1.6.5 - http://znc.in] 14:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-dsrapxzkvwkukgnf] has quit [Quit: Connection closed for inactivity] 16:48 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 17:18 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 240 seconds] 17:33 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 17:41 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #c-lightning 18:18 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 18:27 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 19:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds] 19:21 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:22 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 19:24 -!- tweaks [~tweeeaks@unaffiliated/tweeeaks] has quit [Quit: leaving] 19:36 -!- tweeeaks [~tweeeaks@unaffiliated/tweeeaks] has joined #c-lightning 19:36 -!- tweeeaks is now known as tweaks 19:54 -!- jojeyh [~delphi@2602:306:b8b6:b970:d508:a1ab:fc70:e998] has quit [Ping timeout: 240 seconds] 19:54 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 20:13 -!- jojeyh [~delphi@2602:306:b8b6:b970:480d:4d9:1a02:1755] has joined #c-lightning 20:48 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:58 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 21:16 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 21:30 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 260 seconds] 22:12 -!- freannrak [~ar@m91-129-100-185.cust.tele2.ee] has joined #c-lightning 22:19 -!- freannrak [~ar@m91-129-100-185.cust.tele2.ee] has quit [Ping timeout: 265 seconds] 22:39 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] @decker When I'm setting up Lightning Charge and mounting it to my lightningd instance I get the following error: 22:39 < blockstream_bot> >Starting lightningd... waiting for RPC unix socket... lightningd: Wallet network check failed 22:40 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] Checking the code, it looks like that error is linked to a function that checks the genesis hash of two chains to make sure that they're on the same network 22:41 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] I'm confused as to how this is getting tripped though. Lightningd and Bitcoind are both on mainnet and running fine on their own, and Lightning Charge doesn't interface directly with any chain. 22:52 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] I'm essentially running 22:52 < blockstream_bot> >docker run -u `id -u` -v `pwd`/data:/data -p 9112:9112 -e NETWORK=mainnet -v $HOME/scratch/bitcoin/mainnet/clightning/lightning-rpc -e API_TOKEN=mySecretToken shesek/lightning-charge 22:52 < blockstream_bot> However looking at my server's resource usage logs, bitcoind spikes after that command like crazy, leading me to think that Charge is still creating it's own instance which is where the problem might be 22:52 -!- freannrak [~ar@m91-129-100-185.cust.tele2.ee] has joined #c-lightning 22:56 -!- freannrak [~ar@m91-129-100-185.cust.tele2.ee] has quit [Ping timeout: 256 seconds] 22:57 -!- freannrak [~ar@188.166.55.44] has joined #c-lightning 23:02 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] Nvm I think I got it haha, that did seem to be the case 23:03 < blockstream_bot> [ARIEL DESCHAPELL, Blockstream] Nadav wrote an update to not spin up another bitcoind instance if you're mounting an existing lightningd client, but I just wasn't pointing it at the right directory