--- Day changed Mon Jul 23 2018 00:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 00:16 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 00:16 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has joined #c-lightning 00:16 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has quit [Changing host] 00:16 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 00:47 -!- ken2812221 [~User@180.217.160.31] has quit [Read error: Connection reset by peer] 01:06 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Ping timeout: 268 seconds] 01:14 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 02:56 -!- deusexbeer [~deusexbee@093-092-178-173-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 240 seconds] 02:57 -!- deusexbeer [~deusexbee@095-129-170-057-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 03:10 -!- ken2812221 [~User@1.200.201.180] has joined #c-lightning 03:59 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 03:59 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 04:03 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 04:03 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 256 seconds] 04:35 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:09 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 05:17 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 05:29 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 06:00 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 06:15 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Ping timeout: 260 seconds] 06:33 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 06:41 -!- qubenix [~qubenix@s91904426.blix.com] has joined #c-lightning 06:48 -!- shesek [~shesek@bzq-84-110-60-161.red.bezeqint.net] has joined #c-lightning 06:48 -!- shesek [~shesek@bzq-84-110-60-161.red.bezeqint.net] has quit [Changing host] 06:48 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 06:49 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 06:51 -!- spaced0ut_ [~spaced0ut@198.211.112.88] has joined #c-lightning 06:51 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Remote host closed the connection] 06:51 -!- spaced0ut_ [~spaced0ut@198.211.112.88] has quit [Remote host closed the connection] 06:51 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 07:16 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 07:20 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 07:31 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Quit: Lost terminal] 08:00 -!- ken2812221 [~User@1.200.201.180] has quit [Ping timeout: 260 seconds] 08:18 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-vjlssevaucpdvykt] has quit [Quit: Connection closed for inactivity] 08:36 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has joined #c-lightning 08:36 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has quit [Changing host] 08:36 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 09:21 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:30 -githubby:#c-lightning- [lightning] wythe opened pull request #1734: Updated docs to reflect bech32 default (master...bech32-def) https://git.io/fN8gz 09:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:52 < molz> wondering if i should run the latest master on mainnet 09:57 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-ybpfrqkekzxonrir] has joined #c-lightning 10:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds] 10:19 -!- renepickhardt [588234d5@gateway/web/freenode/ip.88.130.52.213] has joined #c-lightning 10:24 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 10:24 < renepickhardt> hey everyone I have a broken payment channel and the signed transaction cannot be broadcast to the blockchain because one output is correctly being spend. however now I can't access the other unspent output. to me it seems like the output is lost since my channel partner also disappeared. any ideas? 10:25 < renepickhardt> this was the funding transaction: https://www.smartbit.com.au/tx/9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281 10:26 < renepickhardt> as you can see one output was spend (which was the output of my channel partner (interestingly it arrived in my wallet...) however the bigger part of the channel 4.5mBTC are unspent). c lightning is trying to broadcast a transaction but gets error 25 - missing input back from bitcoind (which I understand is a potential doublespend) 10:27 -!- Milkshake [4a3bb05f@gateway/web/freenode/ip.74.59.176.95] has joined #c-lightning 10:28 -!- Milkshake is now known as Guest94548 10:29 -!- Guest94548 [4a3bb05f@gateway/web/freenode/ip.74.59.176.95] has quit [Client Quit] 10:30 < renepickhardt> as you can see one output was spend (which was the output of my channel partner (interestingly it arrived in my wallet...) however the bigger part of the channel 4.5mBTC are unspent). c lightning is trying to broadcast a transaction but gets error 25 - missing input back from bitcoind (which I understand is a potential doublespend) 10:31 < renepickhardt> double spend makes sense since the funding was spend. any idea how I can access the other output? 10:42 -!- Milkshake61 [4a3bb05f@gateway/web/freenode/ip.74.59.176.95] has joined #c-lightning 10:43 -!- ken2812221 [~User@1.200.198.248] has joined #c-lightning 10:47 < Milkshake61> Hi all, how do i set the change my lightning node base fee and a fee rate? i'm cLightning on BitcoinD thanks 10:58 -!- polydin [~delphi@2602:306:b8b6:b970:4157:64ab:75d7:3f2b] has quit [Ping timeout: 276 seconds] 11:00 -!- polydin [~delphi@2602:306:b8b6:b970:b59d:ea7c:1ad2:3484] has joined #c-lightning 11:19 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:33 -!- polydin [~delphi@2602:306:b8b6:b970:b59d:ea7c:1ad2:3484] has quit [Ping timeout: 276 seconds] 11:37 -!- polydin [~delphi@2602:306:b8b6:b970:b59d:ea7c:1ad2:3484] has joined #c-lightning 11:54 -!- booyah [~bb@193.25.1.157] has quit [Remote host closed the connection] 12:44 < renepickhardt> I try to ask my question differently. how can I claim the output of the revocable delivery transaction if for some reason c-lightning has failed to create a correct transaction? 12:55 -!- rusty1 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 268 seconds] 12:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 12:58 < rusty> renepickhardt: Ignore the error 25, that's unrelated: c-lightning spams every tx it's ever wanted into the blockchain. 12:59 < rusty> renepickhardt: re: the transaction, I'd guess you got your output, the other output is the counterparties' and they have to wait for timeout to collect. 12:59 < rusty> Milkshake61: fee-base= and fee-per-satoshi= 13:00 < rusty> Milkshake61: either in the ~/.lightning/config file or using -- options on the command line. 13:08 -!- renepickhardt [588234d5@gateway/web/freenode/ip.88.130.52.213] has quit [Ping timeout: 252 seconds] 13:09 -!- renepickhardt [588234d5@gateway/web/freenode/ip.88.130.52.213] has joined #c-lightning 13:09 < renepickhardt> I did not get my output before the problem occured the channel balance was { "peer_id": "038c04b4c0dcaa2d315a452309f3251d271c5c7d7b08ec7070de355a0fc8dae4fa", "short_channel_id": "530765:2414:0", "channel_sat": 454321, "channel_total_sat": 500000, "funding_txid": "3a5cb1352889e405f27074151dd9641a6d6c5944d21546cf19f805e0420dffae" } 13:09 < renepickhardt> if you look up the funding tx you will see that the 454321 sat that were on my side have not been spent 13:10 < renepickhardt> c.f.: https://www.smartbit.com.au/tx/9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281 13:10 < renepickhardt> where as the other output has been spent and redeemed 13:15 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 13:17 < renepickhardt> also the incident made c-lightning report a crashdump 13:17 < renepickhardt> resend_commitment: Assertion `peer->revocations_received == peer->next_index[REMOTE] - 2' failed. lightning_channeld: Fatal signal 6 0x557d6b12f743 crashdump common/daemon.c:37 0x7f0a2b9d4f1f ??? ???:0 0x7f0a2b9d4e97 ??? ???:0 0x7f0a2b9d6800 ??? ???:0 0x7f0a2b9c6399 ??? ???:0 0x7f0a2b9c6411 ??? ???:0 0x557d6b122566 resend_commitment channeld/channel.c:1701 0x557d6b122 13:44 < molz> renepickhardt, then it's your node that did the force closing? 13:46 < renepickhardt> this is how I interpreted the lock. but the lock time for the revocable spend should be way more than over 13:47 < renepickhardt> the weirdest thing is that the smaller output (which should have belonged to my channel partner) was successfully claimed by my node. so the only way how I can explain this is that my channel partner closed with old channel state and I used his revocation key ( however that does not make sense because nothing about that was in the logs) 13:47 < molz> it seems to me that whoever that owns 0.00454321 BTC 13:47 < molz> amount did the closing and he has to wait for more blocks probably to get the fund back to wallet 13:48 < renepickhardt> closing took place on july 16th that is 1 week 13:48 < renepickhardt> I think I had my node running with maximum of 600 blocks so that should be over. but maybe the channel was negotiated with different settings 13:49 < molz> probably your node had an agreement with an lnd node 13:49 < renepickhardt> so I understand correctly without going into the code I have no chance of trying to spend this output ? 13:49 < molz> and lnd can go up to 2 weeks 13:49 < renepickhardt> I think the partner was either using eclair on mobile or lnd 13:49 < renepickhardt> is there a way in c-lighting how I can see those pending outputs? 13:50 < renepickhardt> or ask it to recollect those? 13:51 < renepickhardt> is information about the situation stored in the sqlite data base or can I just not find out? I mean the script for spending that output ( which would also tell me the locktime ) must be somewhere 13:51 < molz> i don't think you can do anything right now but wait for more blocks 13:52 < renepickhardt> personally no big deal. in general that seems confusing / frustrating for users 13:52 < molz> well do you still have info of this channel on your screen? 13:52 < renepickhardt> no 13:53 < renepickhardt> listfunds does not list any information about the channel anymore 13:53 < molz> so listpeers already forget this channel? 13:53 < renepickhardt> I have some old information which I did safe. 13:53 < renepickhardt> let me check (I would guess yes) 13:54 < molz> i have a c-lightning node and shitcoin.com (LND node) opened a channel to my node, and i see this info on my screen: "our_to_self_delay": 2016, 13:54 -!- polydin [~delphi@2602:306:b8b6:b970:b59d:ea7c:1ad2:3484] has quit [Remote host closed the connection] 13:54 < molz> so it seems c-lightning accepts this condition if i force close his channel, and i have money in the channel i guess i'll have to wait for 2 weeks 13:54 < renepickhardt> yeah list peers does not show it anymore 13:55 < molz> hm ok 13:56 < renepickhardt> so just to recap. c-lighting knows how long it has to wait and it will reclaim the funds once the time is over and from the API I have no chance to inspect the input script of the transaction? 13:56 < renepickhardt> or the meta data of that contract 14:06 < renepickhardt> one more question the website says that the 454321 sat output is a whitness_v0_keyhash so I think with the correct key it should be redeemable right away. the other output was a witness_v0_scripthash 14:11 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 14:13 <@cdecker> renepickhardt: 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:0 is the output owned by the closing party, 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:1 is the closee (which looking at the value should be you) 14:13 <@cdecker> So `listfunds` should show 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:1 as being available, since the other one is the timelocked one 14:14 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:14 <@cdecker> fwiw, 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:0 was later swept into a p2wpkh by tx 03cfab7b726281065bacdefd1d750be218e1601dd1819972b44ea332da1940c8 14:14 < renepickhardt> 03cfab7b726281065bacdefd1d750be218e1601dd1819972b44ea332da1940c8 yeah that is the output that is shown with listfunds 14:15 <@cdecker> So you are the closer, not the closee 14:15 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 14:15 <@cdecker> 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:1 then belongs to the counterparty, and why should you get it back? 14:15 < renepickhardt> well I send an invoice about 454321 satoshi which was paid 14:16 < renepickhardt> and the channel balance as shown above displayed before that I had the balance of 454321 14:16 < renepickhardt> that lets me believe that those where my funds which I should be able to claim 14:18 <@cdecker> Weird, but you are the funder of the channel, aren't you? 14:18 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has joined #c-lightning 14:18 -!- tiagotrs [~user@mue-88-130-108-177.dsl.tropolys.de] has quit [Changing host] 14:18 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 14:18 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 14:18 <@cdecker> How could you receive an incoming payment? 14:19 < renepickhardt> so I send an invoice to the other side which opened a channel with 500000 satoshi and paid the invoice 14:20 < renepickhardt> afther that happened I checked listfunds which showed { "peer_id": "038c04b4c0dcaa2d315a452309f3251d271c5c7d7b08ec7070de355a0fc8dae4fa", "short_channel_id": "530765:2414:0", "channel_sat": 454321, "channel_total_sat": 500000, "funding_txid": "3a5cb1352889e405f27074151dd9641a6d6c5944d21546cf19f805e0420dffae" } 14:20 <@cdecker> Oh, ok, I see, I mixed up the two sides 14:20 <@cdecker> But then how did you get a hold of the change? 14:20 < renepickhardt> as the channel_sat was 454321 I assumed I had the funds 14:20 < renepickhardt> that is the question I am asking 14:21 < renepickhardt> I thought this would be a nice "bug" for me to chase down so I started reading the code in channel.c 14:21 < renepickhardt> but honestly I am to new to the code base in order to understand what is going on... but the main confusing point for me is that I should not have received the other output 14:21 <@cdecker> Were you connected directly to the other side of the payment? And can you ask them if they have the funds now? 14:22 < renepickhardt> I think we had a direct payment channel. I asked the other side 1 week ago but did not receive an answer 14:23 < renepickhardt> it was the first time that I tried out receiving a lightning payment from a person that I don't know. so I don't even know weather the channel partner was technically savvy 14:24 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 244 seconds] 14:24 <@cdecker> Yes, but both funds now sit on p2wpkh which is the final state 14:24 <@cdecker> Oh, sorry, was replying to a message way back 14:25 < renepickhardt> I can send you the tx that lightning tried to spend but looking at that transaction I also understand why the deamon cannot spend this 14:26 < renepickhardt> so yes I see that the unspent output is a p2wpkh. which I understand is the output that should be spendable right away without time lock 14:26 <@cdecker> Yep, can you share the tx that is throwing a missing inputs? 14:26 < renepickhardt> (do I understand that correct?) the other output with the script should be the revocable delivery with the breach remedy path 14:26 < renepickhardt> yeah 14:26 < renepickhardt> as json or hex? 14:26 <@cdecker> hex is fine 14:27 < renepickhardt> 02000000000101aeff0d42e005f819cf4615d244596c6d1a64d91d157470f205e4892835b15c3a0000000000e6090280024fab000000000000160014fa153649a345ec325daf7c62185494060dd77dc2b1ee0600000000002200204c61a0be9bfe850f28827d5d1e253f4a2a2998b1b9ae69c4bcaa3fb9b10868bc040047304402203c98efe3b9f7b24774385da5d7bf2982fe57ee24f56a0ad2f4d18dbfbc24416d0220423771f429065ccf2f0145c9eb010e962ec99e8532a468db90b5840fdc5d82e501483045022100dc8c33c09966b9603910 14:27 <@cdecker> Can you share that in a paste (IRC lenght limitations) 14:28 < renepickhardt> sure 14:28 < renepickhardt> https://pastebin.com/01c55AgA 14:29 <@cdecker> Oh, nvm, that's your own unilateral closing transaction, that one would have meant you close the channel and it is conflicting with the remote one 14:29 < renepickhardt> not sure if I can follow 14:30 < renepickhardt> in my uniliteral closing my funds would be locked 14:30 < renepickhardt> why would I get the output of the channel partner? 14:30 < renepickhardt> in particular if it was my node that closed it. or do you say both sides tried to do an uniliteral closing? 14:31 <@cdecker> Yeah, you saw the other side closing and tried to do the same (unsuccessfully) 14:31 < renepickhardt> ok that makes sense. because the one output in my transaction (the smaller amount) was spent 14:32 <@cdecker> This was doomed since it conflicts with the remote side, so don't worry about not being able to send that tx 14:32 < renepickhardt> but what about the UTOX in my oppionion I should be able with some key derieved from my hsm_secret to spent it 14:33 < renepickhardt> sure that makes sense (double spent of funding tx is impossible) and I see that the funding was spent (and obviously not with my version) 14:33 < renepickhardt> so it looks to me that when the other side send a ctx it was an old one and I used their revocation key to claim their output? 14:34 <@cdecker> The their_unilateral/to_us output (which is the one which is missing) is a bit more complicated because it mixes in the commitment point for the state 14:34 < renepickhardt> what exactly is the commitment point? 14:35 < renepickhardt> or where in the code could I read this? 14:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:35 < renepickhardt> I think I have a good theoretical grasp of the situation by now (thanks for taking the time to explain in dept) 14:38 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 14:38 <@cdecker> The details for the keys are here https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md#localpubkey-remotepubkey-local_htlcpubkey-remote_htlcpubkey-local_delayedpubkey-and-remote_delayedpubkey-derivation 14:38 <@cdecker> I'm more confused by the minute :-) 14:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:40 <@cdecker> 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:1 should be yours by all the info I have, but for some reason you got 9900aeaa5d6d8aedb5b9074999de48faa7ff6bd9ea6b733542d8760e9950d281:0 14:40 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 14:41 < renepickhardt> per commitment point the same as per commitment secret? 14:41 <@cdecker> A good point to start looking into the key derivation in c-lightning might be this one https://github.com/ElementsProject/lightning/blob/05d4e8519cecd00f76270e46952d78bef29d1552/hsmd/hsm.c#L592-L608 14:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 14:41 <@cdecker> Yep 14:41 <@cdecker> (should be...) 14:42 < renepickhardt> actually I went to irc because I thought it would be easier to chase that bug. but if you wish I could file an issue and describe the situation 14:42 < renepickhardt> I didn't want to got to the bug tracker because I wanted to kind of fix this myself (but as said I am not deep enough in the code base yet) 14:48 <@cdecker> Maybe filing an issue so we can coordinate is best 14:49 <@cdecker> Should make information sharing easier 14:50 < renepickhardt> yeah I will do that also study bolt 3 in more detail tomorrow. it is interesting I am just reading this with heaving the situation in mind and I realize how much stuff is not sufficiently clear for me 14:53 < renepickhardt> following bug title precise enough? lost p2wkh after unilateral close from peer with successful claimed output from revocable delivery transaction 15:08 -githubby:#c-lightning- [lightning] jb55 opened pull request #1735: tools: fix bash path in check-manpage.sh (master...check-manpage-fix) https://git.io/fN4fi 15:11 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 248 seconds] 15:21 -githubby:#c-lightning- [lightning] jb55 opened pull request #1736: doc: update python test requirements in HACKING (master...hacking-python-deps) https://git.io/fN4J1 15:35 -githubby:#c-lightning- [lightning] jb55 closed pull request #1736: doc: update python test requirements in HACKING (master...hacking-python-deps) https://git.io/fN4J1 15:37 -!- renepickhardt [588234d5@gateway/web/freenode/ip.88.130.52.213] has quit [Ping timeout: 252 seconds] 15:40 -githubby:#c-lightning- [lightning] cdecker pushed 24 new commits to master: https://git.io/fN4Uy 15:40 -githubby:#c-lightning- lightning/master 26deec0 Rusty Russell: channeld: remove duplicate call to channel_announcement_negotiate().... 15:40 -githubby:#c-lightning- lightning/master 9dd0415 Rusty Russell: channeld: don't free msg in init.... 15:40 -githubby:#c-lightning- lightning/master 289e39a Rusty Russell: bitcoin/pubkey: add pubkey_from_secret.... 15:41 -!- antanst_ [~antanst@62.169.219.213] has quit [Ping timeout: 240 seconds] 15:56 -!- qubenix [~qubenix@s91904426.blix.com] has quit [Remote host closed the connection] 16:24 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 16:24 < Chris_Stewart_5> Does c-lightning have to do a sync against bitcoind when you fire it up for the rest time? 16:25 < Chris_Stewart_5> i.e. my c-lightning instance says it is at block 404964, but my bitcoin-cli is at 1355162 16:38 < molz> Chris_Stewart_5, yes i think c-lightning node has to be synced to bitcoind 16:39 < molz> and then it updates the network 16:40 < Chris_Stewart_5> molz: interesting, so c-lightning has it's own IBD? 16:40 < molz> im not sure 16:42 < Chris_Stewart_5> I'm wondering if I screwed up some sort of configuration with my lightning-charge instance, and it launched a parallel bitcoind inside of docker 16:42 < Chris_Stewart_5> It doesn't seem to make sense to me why we would do "IBD" for lightningd 16:46 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/fN4L6 16:46 -githubby:#c-lightning- lightning/master 369bd27 Mark Beckwith: Updated docs to reflect bech32 default... 17:23 < grubles> your bitcoind is at block 1,355,162? 17:25 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1735: tools: use /usr/bin/env bash instead of /bin/bash (master...check-manpage-fix) https://git.io/fN4fi 17:26 < Chris_Stewart_5> grubles: yes, testnet 17:28 < grubles> oh hah 17:47 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning 18:00 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 18:06 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 256 seconds] 18:08 -!- jpe__ [~jpe@200116b8428cf000f1d13b0cf629ac66.dip.versatel-1u1.de] has joined #c-lightning 18:11 -!- jpe_ [~jpe@200116b8420fc3004c35767b739c9fcd.dip.versatel-1u1.de] has quit [Ping timeout: 260 seconds] 18:19 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has joined #c-lightning 18:46 -!- tiagotrs_ [~user@i577B9AD7.versanet.de] has joined #c-lightning 18:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 18:50 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 18:54 -!- tiagotrs_ [~user@i577B9AD7.versanet.de] has quit [Ping timeout: 264 seconds] 19:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:03 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 19:13 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 256 seconds] 20:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds] 20:37 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 21:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:18 -!- grafcaps [~haroldbr@050-090-083-229.res.spectrum.com] has quit [Ping timeout: 260 seconds] 21:37 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 21:58 -!- grubles_ [~grubles@unaffiliated/grubles] has joined #c-lightning 21:58 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 244 seconds] 22:02 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 22:02 -!- dougsland [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds] 22:19 -!- shesek [~shesek@bzq-84-110-232-73.red.bezeqint.net] has joined #c-lightning 22:19 -!- shesek [~shesek@bzq-84-110-232-73.red.bezeqint.net] has quit [Changing host] 22:19 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning