--- Day changed Mon Feb 05 2018 00:01 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 276 seconds] 00:32 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 00:33 < miklolFi> is there a reason why I cannot see my mainnet node here: https://lnmainnet.gaben.win 00:35 < rompert> it is a bit stalled. you can use my mirror until the original gets fixed 00:35 -!- jojeyh [~delphi@2602:306:b8b6:b970:d410:b884:55b7:f0af] has quit [Ping timeout: 276 seconds] 00:35 < rompert> https://lnmainnet.rompert.com/ 00:38 < miklolFi> found it! thanks! 00:38 < rompert> miklolFi: i don't see any new nodes added the latest three hours though ? is it there? https://www.robtex.com/lightning/node/?sort=-discovered 00:39 < miklolFi> My node has been running 48h now :) 00:39 < rompert> oh :) 00:52 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #731: Expiration revamp (master...expiration-revamp) https://git.io/vNVHx 00:59 -!- lxer [~lx@95.91.213.129] has joined #c-lightning 01:29 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #883: Status improvements (master...status-improvements) https://git.io/vNNf0 01:51 -!- Mark__ [5bd4cf04@gateway/web/freenode/ip.91.212.207.4] has joined #c-lightning 02:23 < lxer> what is the meaning of max_htlc_value_in_flight_msat ? 02:31 -!- shesek [~shesek@bzq-84-110-233-145.cablep.bezeqint.net] has joined #c-lightning 02:31 -!- shesek [~shesek@bzq-84-110-233-145.cablep.bezeqint.net] has quit [Changing host] 02:31 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 02:49 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNhIk 02:49 -githubby:#c-lightning- lightning/master e4d719a Sjors Provoost: [doc] install: add libsodium-dev 02:52 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning 03:04 < bitonic-cjp> bitonic-cjp says hi :-) 04:29 < p3tr> clightning has its own wallet right? where is it stored? 04:32 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 04:36 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 04:52 -!- Dmtr [4ebaa66a@gateway/web/freenode/ip.78.186.166.106] has joined #c-lightning 05:01 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 05:02 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 05:07 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Remote host closed the connection] 05:12 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:13 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 05:34 < Dmtr> hi 05:36 < bitonic-cjp> Where can I learn about the C-lightning source code? 05:37 < bitonic-cjp> So far, I found this: 05:37 < bitonic-cjp> https://github.com/bitonic-cjp/lightning/blob/master/doc/HACKING.md 05:37 < bitonic-cjp> https://github.com/ElementsProject/lightning/issues/614 05:53 -!- miklolFi [~miklolFi@78.27.126.165] has joined #c-lightning 06:00 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 06:31 -!- jperau [~jason@re.permietech.com.au] has quit [Quit: Ex-Chat] 06:54 -!- ruby32 [~ruby32@158.106.219.26] has joined #c-lightning 06:54 < lxer> bitonic-cjp: what do you mean exactly? 06:57 < lxer> p3tr: no, there is no wallet 07:00 < bitonic-cjp> I'd like to get a sort of a "map" of the source code: how is it designed architecturally, what can I find where? 07:04 < p3tr> lxer: hm, so where does the address that i get when doing 'newaddr' come from? 07:05 < p3tr> bitonic-cjp: i would like to get it too :) 07:06 < lxer> p3tr: good point. I assumed from bitcoind, but perhaps not 07:07 < p3tr> sending money to clightning from my bitcoin wallet involves a onchain tx, so i thought clightning keeps its own wallet somewhere 07:07 < p3tr> but i can't seem to find it... i would really like to have a backup of it in case my vm dies 07:08 < p3tr> or if there is no wallet then i would like to know what newaddr does and how it all works :) 07:11 -!- Dmtr [4ebaa66a@gateway/web/freenode/ip.78.186.166.106] has quit [Quit: Page closed] 07:13 < bitonic-cjp> p3tr: From what I know, a a lot of secrets (has pre-images, private keys) are derived from hsm_secret. Maybe in practice you also need a copy of lightningd.sqlite3 though. 07:14 < p3tr> bitonic-cjp: yeah i'm backing up hsm_secret but having no idea if thats enough is kinda scary... and i like to understand stuff i plan to use :) 07:14 < bitonic-cjp> But I get that it would be VERY nice to have (1) a lightningd that CAN be backed up and (2) a guide on how to do that. 07:14 < p3tr> might add that sqlite3 db to backups just in case 07:15 < lxer> not sure, but I think it is enough. It uses bip32 to generate addresses 07:15 < lxer> p3tr: you use it on mainnet? 07:15 < p3tr> lxer: not _yet_, first i want to get the hang of it on testnet 07:15 < lxer> ok, take your time. it crashes often 07:16 < p3tr> yeah i saw a couple of crashes already 07:17 < bitonic-cjp> I'd like to know what happens if your hard disk crashes, you get another computer, install C-Lightning and restore a back-up of (only!) hsm_secret. Will it recover everything automatically? 07:17 < p3tr> bitonic-cjp: thats actually what i'm planning to test (probably tomorrow) :) 07:18 < p3tr> if restoring the hsm_secret magically brings back all my funds and channels 07:19 < bitonic-cjp> I expect it won't, if hsm_secret is only the root of your cryptographic secrets. 07:19 < bitonic-cjp> I'm going to have a look inside the .sqlite right now. 07:19 < p3tr> let me know what you find 07:21 < bitonic-cjp> 07:24 < bitonic-cjp> tables: channel_configs, channel_htlcs, channels, invoices, outputs, payments, peers, shachain_known, shachains, vars, version 07:25 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 07:32 < lxer> Is there a clightning Slack channel somewhere? it seems somewhat dead in here 07:35 < p3tr> bitonic-cjp: it seems to me one would probably want to backup the sqlite too - i guess thats where the commitment tx are kept? so without the sqlite there would be no way of protecting yourself from theft in case of old commitment broadcast from counterparties 07:36 < p3tr> which also means that backing up that sqlite would ideally be done after every channel update... hm 07:37 < p3tr> could be quite intense for big nodes if that is the case 07:37 < bitonic-cjp> When recovering from an old backup, there might be the risk of using an outdated commit tx. If you ever broadcast that, you risk losing all your channel funds to an evil peer. 07:38 < p3tr> yeah and that peer wouldn't even be evil right? since YOU broadcast old tx, so to an observer it would seem YOU are trying to steal 07:38 < p3tr> (if that old tx is in your favor ofc) 07:38 < bitonic-cjp> There was this idea that, on re-connect, peers would ALWAYS ask each other for the latest commit tx; I don't know if that ended up in the standard. 07:38 < bitonic-cjp> true. 07:40 < p3tr> on the other hand, this risk only applies if an unilater channel close occurs... so even if you don't have the latest commitment tx you can still be lucky (if the counterparty is honest) and everything will be well 07:40 < p3tr> anyway, adding the sqlite to my backups :) 07:53 < bitonic-cjp> Is wallet a separate daemon, or part of lightningd? 07:58 < miklolFi> I made a backup from /.lightning folder. Then I deleted everything and I had "new" wallet after that. Then I deleted everything again and restored backup files and all channels etc. were back. 08:00 < miklolFi> I didnt try it on other computer but I suppose it should work 08:04 < bitonic-cjp> Yes, that makes sense. A bit risky would be to only backup hsm_secret. I guess that won't work. 08:04 < bitonic-cjp> Another risky test would be (1) make a back-up of everything, (2) do some transactions, (3) restore the back-up. 08:23 -!- miklolFi [~miklolFi@78.27.126.165] has quit [Remote host closed the connection] 08:40 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 08:45 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Ping timeout: 256 seconds] 08:46 -githubby:#c-lightning- [lightning] icota opened pull request #918: Fix listpeers JSON command description (master...fix-listpeers-description) https://git.io/vNhD0 09:01 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 09:02 < bitonic-cjp> Does C-Lightning store any network topology information? I can't find it in lightningd.sqlite3. 09:07 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 240 seconds] 09:18 < ianthius> bitonic-cjp: p3tr: Yes, you ware going to want to backup both the DB and the secret 09:19 < bitonic-cjp> kthx 09:19 < ianthius> from what I have deduced from the source code, addresses are derived from the secret and the DB holds all the channel data and what outputs have been used, etc. 09:19 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving] 09:20 < ianthius> presumably you could recover your funds with just the HSM secret... but you would need to wait for all your channels to time out and be closed.. 09:21 < ianthius> backing up the DB should be done very regularly i think... great questions though.. 09:43 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 09:47 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 10:00 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Remote host closed the connection] 10:10 -!- Mark__ [5bd4cf04@gateway/web/freenode/ip.91.212.207.4] has quit [Ping timeout: 260 seconds] 10:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 10:19 < rusty> cdecker: confused about your comment on https://github.com/ElementsProject/lightning/pull/763 ? 10:19 < rusty> cdecker: I rebased and fixed JSON API update, but the issue is the python wrapper wraps newaddr and doesn't pass the new optional arg through. 10:23 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNhAn 10:23 -githubby:#c-lightning- lightning/master a0dffc7 Igor Cota: Fix listpeers JSON command description 10:28 -githubby:#c-lightning- [lightning] rustyrussell pushed 15 new commits to master: https://git.io/vNhAF 10:28 -githubby:#c-lightning- lightning/master 0bc2f87 Christian Decker: gossip: Added uintmap based channels map, indexed by scids... 10:28 -githubby:#c-lightning- lightning/master d7224e2 Christian Decker: gossip: Added short_channel_id_to_uint for uintmap index... 10:28 -githubby:#c-lightning- lightning/master 60ab947 Christian Decker: gossip: Add new channels to channels map... 10:35 -!- Relaxx [5b59c554@gateway/web/freenode/ip.91.89.197.84] has joined #c-lightning 10:39 -!- Relaxx [5b59c554@gateway/web/freenode/ip.91.89.197.84] has left #c-lightning [] 10:40 -!- Relaxx [5b59c554@gateway/web/freenode/ip.91.89.197.84] has joined #c-lightning 10:48 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 10:48 -githubby:#c-lightning- [lightning] cdecker opened pull request #920: wallet: Re-introduce change assertion for withdrawals (master...withdraw-to-self) https://git.io/vNhh4 10:59 < grubles> has anyone attempted building on openbsd yet 11:06 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 11:10 -!- chiwwers [5e6e3ddb@gateway/web/freenode/ip.94.110.61.219] has joined #c-lightning 11:11 < chiwwers> I'm not sure if this is the right place to ask but here we go: To run a lightning node I followed the instructions here: https://medium.com/@dougvk/run-your-own-mainnet-lightning-node-2d2eab628a8b except that I downloaded and installed bitcoind and lightningd from source and not in a docker. I can fund my on-chain wallet, connect to peers but when I try to open a channel the daemon crashes. 11:12 < chiwwers> with the following message in crash.log: +61107.734361005 lightningd(30005):BROKEN: wallet_channel_save: UPDATE channels SET fundingkey_remote=?, revocation_basepoint_remote=?, payment_basepoint_remote=?, htlc_basepoint_remote=?, delayed_payment_basepoint_remote=?, per_commit_remote=?, old_per_commit_remote=?, local_feerate_per_kw=?, remote_feerate_per_kw=?, channel_config_remote=? WHERE id=?: no such column: local_feerate_per 11:13 < chiwwers> Anyone here who could help me out? Would be much appreciated :) 11:18 < p3tr> chiwwers: um, so you compiled bitcoin core from master? 11:19 < p3tr> if that is the case i would try just downloading binaries (version 15.1) and trying again with that 11:19 < p3tr> (or compile 15.1 if you insist on compiling) 11:27 < Relaxx> i created a simple network in gns3 to do some experiments with the lightning docker. im able to fund channels, do some payments and close them. but i dont know how to fund a channel which both parties have funds from beginning. atm its only the creator of the channel who has all funds of the channel. can anybody help me, or is there no way to fund a channel with balance on each side? :) 11:29 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [Remote host closed the connection] 11:29 -!- chiwwers [5e6e3ddb@gateway/web/freenode/ip.94.110.61.219] has quit [Quit: Page closed] 11:29 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 11:39 -!- CubicEar_ [~cubiceart@190.140.125.142] has joined #c-lightning 11:43 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 11:46 < lxer> chiwwers: dont use mainnet. 11:49 -githubby:#c-lightning- [lightning] laanwj opened pull request #921: gossipd: Move include of time.h to routing.h (master...2017_02_freebsd_compile) https://git.io/vNjTq 12:00 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning 12:12 -!- Relaxx [5b59c554@gateway/web/freenode/ip.91.89.197.84] has quit [Quit: Page closed] 12:27 -!- tweeaks is now known as tweaks 12:30 -githubby:#c-lightning- [lightning] laanwj opened pull request #922: lightningd: Don't crash when libunwind backtrace not available (master...2017_02_libunwind) https://git.io/vNjqq 12:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 12:50 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-asrqrdujrzolxtlu] has joined #c-lightning 13:15 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 14:11 -!- lio1760 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 14:23 -!- lio17 [~lio17@ns350827.ip-37-187-174.eu] has quit [Quit: lio17] 14:44 -!- lio1760 [~lio17@80.ip-145-239-89.eu] has quit [Quit: lio1760] 14:45 -!- lio1760 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 15:12 -!- lio1760 is now known as lio17 15:12 -!- beeteecee [~beeteecee@199.66.90.209] has quit [Ping timeout: 256 seconds] 15:13 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Quit: lio17] 15:14 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 15:34 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #923: test_lightningd: Increase times in expiration waiting test. (master...expire-wait-timeouts) https://git.io/vNjgT 15:35 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 268 seconds] 15:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:36 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Quit: lio17] 15:37 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 15:37 -!- lio17 [~lio17@80.ip-145-239-89.eu] has quit [Client Quit] 15:38 -!- lio17 [~lio17@80.ip-145-239-89.eu] has joined #c-lightning 16:02 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has joined #c-lightning 16:10 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-asrqrdujrzolxtlu] has quit [Quit: Connection closed for inactivity] 16:17 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 16:44 -!- lxer [~lx@95.91.213.129] has quit [Ping timeout: 268 seconds] 16:46 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has quit [Quit: leaving] 16:47 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #924: Travis finegrained tests (master...travis-finegrained-tests) https://git.io/vNjrQ 17:03 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has joined #c-lightning 17:07 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #925: channeld: don't send announcement_signatures if we're shutting down. (master...announcement-signatures-during-closing) https://git.io/vNjoj 17:12 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 17:12 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 17:15 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has quit [Ping timeout: 256 seconds] 17:35 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNj6y 17:35 -githubby:#c-lightning- lightning/master 1ef7985 Wladimir J. van der Laan: lightningd: Don't crash when libunwind backtrace not available... 17:36 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #921: gossipd: Move include of time.h to routing.h (master...2017_02_freebsd_compile) https://git.io/vNjTq 17:37 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNj67 17:37 -githubby:#c-lightning- lightning/master 4fd7e26 Christian Decker: wallet: Re-introduce change assertion for withdrawals... 17:38 -githubby:#c-lightning- [lightning] rustyrussell pushed 6 new commits to master: https://git.io/vNj6p 17:38 -githubby:#c-lightning- lightning/master 37ea24e William Casarin: newaddr: support bech32 p2wpkh funding addresses... 17:38 -githubby:#c-lightning- lightning/master b30fb95 William Casarin: chainparams: fix regtest bip173_name... 17:38 -githubby:#c-lightning- lightning/master 0e59e09 William Casarin: test: switch invoice tests to use proper bip173 name... 17:47 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has joined #c-lightning 17:52 -!- grafcaps [~haroldbr@50-255-209-133-static.hfc.comcastbusiness.net] has quit [Ping timeout: 248 seconds] 18:00 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 18:05 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Ping timeout: 256 seconds] 18:28 -!- CubicEar_ [~cubiceart@190.140.125.142] has quit [Remote host closed the connection] 18:29 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 18:33 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 18:33 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [Ping timeout: 256 seconds] 18:42 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 260 seconds] 18:48 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 18:50 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 18:50 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #923: test_lightningd: Increase times in expiration waiting test. (master...expire-wait-timeouts) https://git.io/vNjgT 18:51 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 18:55 < grafcaps> I've been running a c-lightning node for about two weeks and I want to update to the latest commit. Is there anything that I need to do before re-compiling? For instance, should I close all channels and move my tBTC out of the wallet first? 19:05 < rusty> grafcaps: it should "Just Work"... 19:07 < grafcaps> oh goodie! 19:09 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #c-lightning 19:40 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 19:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-plovapgqdbvplnyh] has joined #c-lightning 20:08 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 20:20 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #924: Travis finegrained tests (master...travis-finegrained-tests) https://git.io/vNjrQ 20:23 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #926: Wire generation and status improvements (master...status-improvements) https://git.io/vNjHk 20:38 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 260 seconds] 20:44 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning 22:08 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 22:11 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-plovapgqdbvplnyh] has quit [Quit: Connection closed for inactivity] 22:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 22:24 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [Remote host closed the connection] 22:36 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 240 seconds] 23:08 -!- jojeyh [~delphi@2602:306:b8b6:b970:d98b:b647:e8bb:7960] has joined #c-lightning 23:57 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 23:57 -!- lxer [~lx@ip5f5bd581.dynamic.kabel-deutschland.de] has joined #c-lightning