--- Day changed Thu Aug 02 2018 00:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 00:45 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-scaxogueuhvchydv] has quit [Ping timeout: 256 seconds] 00:45 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Remote host closed the connection] 01:04 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 02:26 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-awrwteihnitsaeej] has quit [Quit: Connection closed for inactivity] 02:40 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-teafsgvxaoqmxuah] has joined #c-lightning 02:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 04:05 -!- NicolasDorier_ [sid129442@gateway/web/irccloud.com/x-qdejdtetwaoavkex] has quit [Remote host closed the connection] 04:35 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 04:39 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Ping timeout: 260 seconds] 05:13 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:53 < blockstream_bot> [Parth Choudhary, Blockstream] how long does it take usually to reflect funds via `lightning-cli listfunds` when you transfer funds using ` bitcoin-cli -testnet sendtoaddress` 05:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 05:54 < blockstream_bot> [Parth Choudhary, Blockstream] Also why don't the funds get reflected on an address created by `lightning-cli newaddr` and funding using a faucet. 06:01 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds] 06:06 <@cdecker> Parth: `listfunds` will show the funds as soon as they have 1 confirmation (c-lightning scans the blockchain, not the memory pool) 06:06 <@cdecker> Parth: Don't understand what you meant by "funds get reflected on an address" 06:13 < blockstream_bot> [Parth Choudhary, Blockstream] So i created an address using `lightning-cli newaddr` with c-lightning running on testnet and funded this address using a faucet. But the when I run `listfunds`(even after 6 confirmations) the response is `{ 06:13 < blockstream_bot> "outputs": [ 06:13 < blockstream_bot> ], 06:13 < blockstream_bot> "channels": [ 06:13 < blockstream_bot> ] 06:13 < blockstream_bot> }` 06:20 < jb55> think I'm going to try and build an opengl visualization daemon today 06:20 < jb55> daemon instead of rpc because I want realtime access to all the nitty gritty 06:20 < jb55> would be cool to see glowing edges on channel updates and such 06:27 < jb55> guess it would be more of a client that a daemon. maybe it might be better persuing a pubsub api first? 06:33 < molz> Parth, when you do `lightning-cli newaddr` it gives you a bech32 address which is not used by most faucets 06:34 < molz> Parth, try `lightning-cli newaddr help` and get the other type of address 06:37 < blockstream_bot> [Parth Choudhary, Blockstream] Alright, Thanks! 06:39 < blockstream_bot> [Parth Choudhary, Blockstream] I was using https://testnet.manu.backend.hamburg/faucet mentioned on https://github.com/ElementsProject/lightning. Will use the other one and see if that works. 06:48 < jb55> I've updated the README since this has been tripping people up a few times now https://github.com/ElementsProject/lightning/pull/1797 06:55 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 07:13 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 07:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 07:56 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 07:57 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-qmcjuudscmcbfplo] has joined #c-lightning 07:57 < Lightblock_> Hello 07:57 < Lightblock_> @cdecker 07:57 < Lightblock_> for example I take a random nodeid from some public explorer 07:57 < Lightblock_> 1ml.com for example 07:57 < Lightblock_> ask about this node from my c-lightning daemon 07:58 < Lightblock_> and I receive empty json object 07:58 < Lightblock_> there are hundreds of such nodes 07:58 < Lightblock_> how come my c-lightning does not know about them? 07:58 < Lightblock_> same goes for channels 07:58 < Lightblock_> listnodes 07:59 < Lightblock_> returns me an empty json object 08:05 < Lightblock_> anyone has any thoughts? 08:19 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 08:23 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 08:24 < Chris_Stewart_5> Why would sync take so long for c-lightning if bitcoind is synced? 08:24 -!- moneyball [sid299869@gateway/web/irccloud.com/x-wgtpedddrqknzuwj] has joined #c-lightning 08:24 < Chris_Stewart_5> I had a user of my lapp last night sync bitcoind, and then it took another 2 hours for c-lightning to sync 08:33 < Lightblock_> no, actually the sync speed seems to be decent 08:34 < Lightblock_> my only concern is why c-lightning is not seeing so many nodes? 08:34 < Lightblock_> like it is running behind 08:34 < Lightblock_> also the parameters of channels like capacity etc changes 08:34 < Lightblock_> but c-lightning is also very slow to pick them up 08:34 < moneyball> what might explain the slow sync time? the cpu utilization for lightningd was 1 hour 49 minutes to go from block height 0 to 1356635 08:35 < Lightblock_> no actually the speed of initial sync is decent 08:36 < Lightblock_> the main concern is why c-lightning is not seeing so many nodes? 08:36 < moneyball> to be clear, you are saying many hours is decent? or, my experience is atypical? 08:36 < Lightblock_> it's days 08:36 < Lightblock_> not hours 08:36 < Lightblock_> also the parameters of channels change very oftern 08:37 < Lightblock_> but c-lightning is really slow to pick up the changes 08:38 < Chris_Stewart_5> Lightblock_: When did you last try to sync c-lightning from scratch? 08:39 < Chris_Stewart_5> It seems that moneyball had to do IBD twice 08:40 < Lightblock_> I assumed that it only needs to be launched once? 08:40 < Lightblock_> and the update process is ongoing 08:40 < Lightblock_> I have checked the node frequently 08:41 < Lightblock_> and it is always up and running 08:41 < Lightblock_> the bitcoind is also running constantly 24/7 08:41 < Lightblock_> what do you mean by syncing c-lightning from scratch? what is the relvant cli command for that? 08:42 < Lightblock_> would be thankful ofr that 08:42 < Chris_Stewart_5> It just seems strange that it would not do this in lockstep. The behavior we saw was "wait for bitcoind to sync, and then sync all of lightningd" 08:43 < moneyball> i got the blockheight using $cli/lightning-cli getinfo 08:44 < moneyball> and for bitcoind, bitcoin-cli -testnet getblockcount 08:44 < moneyball> the bitcoind block height went from 0 to 1356551 and THEN the lightning block height went from 0 to 1356635 08:46 < Lightblock_> I am on mainnet 08:52 < Lightblock_> just ran getinfo for lightning cli and getblockchaininfo for bitcoind 08:53 < Lightblock_> both are on the latest mainnet block 534861 08:53 < Lightblock_> so everything is up-to-date here 08:55 < Lightblock_> just took a random node 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 08:55 < Lightblock_> and asked listnodes 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 08:55 < Lightblock_> why am I receiving an empty answer? 08:55 < Lightblock_> thus c-lightning does not know about this node 09:01 < Lightblock_> not sure I am talking about something relevant ) 09:21 < Chris_Stewart_5> \q 09:23 < Chris_Stewart_5> we are also seeing more routing weirdness where a node has a direction connection to another node, and a channel open and we are getting route not found errors 09:45 < Chris_Stewart_5> Is there a reason a channel would get stuck in "status": [ "Funding channel: offered, now waiting for accept_channel" ] state? 09:45 < Chris_Stewart_5> we are trying to open a channel from c-lightning to eclair 09:48 -!- ken2812221 [~User@180.217.140.78] has quit [Ping timeout: 276 seconds] 10:49 -!- ken2812221 [~User@180.217.182.131] has joined #c-lightning 10:57 < moneyball> also, the lightning-cli fundchannel command hangs (probably waiting for the channel to be accepted) 11:05 < Chris_Stewart_5> cdecker: ^ 11:15 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has quit [Remote host closed the connection] 11:40 < moneyball> also fyi i'm using v0.6 of c-lightning 11:45 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-qmcjuudscmcbfplo] has quit [Quit: Connection closed for inactivity] 11:54 < blockstream_bot> [Christian Decker, Blockstream] Lightblock: c-lightning is very quick at syncing gossip, and unlike 1ml we prune nodes that have no channels, or haven't been seen in 1 week as the spec says 11:55 < blockstream_bot> [Christian Decker, Blockstream] So it's 1ml showing loads of stale entries that are useless for routing 11:55 < blockstream_bot> [Christian Decker, Blockstream] Chris: fundchannel should not hang if the peer is connected and responding. It might be the other side that is unresponsive 11:56 < moneyball> fyi it finally exited with "{ "code" : -1, "message" : "Owning subdaemon lightning_openingd died (62208)" }" 11:56 < blockstream_bot> [Christian Decker, Blockstream] As for the route not being found, that could be because the channel is not confirmed, doesn't have sufficient capacity, or is simply offline 11:56 < blockstream_bot> [Christian Decker, Blockstream] Yep, that means the connection died 11:58 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 240 seconds] 12:33 < moneyball> i think we have it figured out 14:14 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 15:04 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 15:47 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 15:56 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-ghsfbaacbokkbnan] has joined #c-lightning 15:56 < Lightblock_> any comments from devs would be really appreciated 16:03 <@cdecker> Lightblock_: I am one of the devs, 1ml is just showing stale entries that c-lightning will prune correctly according to the spec 16:05 < Lightblock_> thanks for reply, highly appreciated, why do you say stale? It appears that those nodes are updated just recently 16:05 < Lightblock_> like few minutes ago or so 16:05 < Lightblock_> I mean how can you definde whether the node is stale or really a freshly updated one? 16:06 < Lightblock_> I have no other tools besides my lightning daemon which I can query 16:06 <@cdecker> Do those nodes have active channels? 16:07 <@cdecker> If they do not, they are not considered valid nodes according to the gossip protocol, and are likely spam 16:07 < Lightblock_> gonna check now 16:08 < Lightblock_> actually they do... 16:09 < Lightblock_> for example 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 16:10 <@cdecker> Just sync'd and it works 16:10 <@cdecker> Synchronizing took my node 16 seconds 16:12 < Lightblock_> please advise what do you mean by sync? 16:12 < Lightblock_> I have it on autopilot on a dedicated server 16:12 < Lightblock_> the node is running 24/7 16:12 < Lightblock_> isn't it syncing itself? 16:13 < Lightblock_> what is a cli command for a force sync? 16:15 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 16:16 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Ping timeout: 240 seconds] 16:20 < Lightblock_> @cdecker so you are seeing 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 details on your node via listnodes now? 16:25 <@cdecker> Yes, I am 16:25 <@cdecker> It is syncing by itself, no need to manually trigger 16:27 < Lightblock_> strange 16:27 < Lightblock_> I have made force shut down 16:27 < Lightblock_> and then relaunched the node 16:27 < Lightblock_> and here you go 16:27 < Lightblock_> all the node that I was missing I can see now 16:28 < Lightblock_> very strange, I had the node running as daemon for about 2 months now and assumed that I have the latest state 16:29 < Lightblock_> given that my bitcoind getblockchaininfo and lightning cli always showed the latest blockheight 16:30 < Lightblock_> I guess I have to restart it every morning then ) 16:32 < Lightblock_> will observe its behavior further 16:57 < molz> i can see that node too 16:57 < molz> ~$ lightning-cli listnodes | grep 03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71 16:57 < molz> "nodeid": "03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71", 17:00 < grubles> are preimages secret? ie. probably not a good idea to make them public? 17:00 < molz> i think so 17:03 < grubles> what if it is for an invoice that has been paid 17:05 < molz> if the payor pays then he gets to know the preimage and can show to the receiver he's paid 17:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 18:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 18:23 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Read error: Connection reset by peer] 18:38 -!- arowser [~arowser1@23.83.244.223.16clouds.com] has quit [Ping timeout: 240 seconds] 18:53 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-ghsfbaacbokkbnan] has quit [Quit: Connection closed for inactivity] 21:07 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-wbbcoczlmbtqfski] has joined #c-lightning 21:37 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 22:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 22:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 23:08 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 23:34 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Read error: Connection reset by peer]