--- Log opened Sat Mar 16 00:00:17 2019 00:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 02:04 -!- kexkey [~kexkey@139.28.218.6] has quit [Ping timeout: 246 seconds] 03:55 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 04:05 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 05:05 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning 05:09 -!- m-schmoock [~will@schmoock.net] has quit [Quit: leaving] 05:09 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning 05:13 -!- m-schmoock [~will@schmoock.net] has quit [Client Quit] 05:13 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 05:13 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 05:13 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 05:16 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning 05:56 < m-schmoock> cdecker: updated the setchannelfee 'all' feature to master after rusty's refinements pulled in. 05:56 < m-schmoock> https://github.com/ElementsProject/lightning/pull/2470 07:54 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 08:03 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 08:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 08:09 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 08:19 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 08:24 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 252 seconds] 08:36 -!- raucao [~raucao@skippe2.nine.ch] has quit [Ping timeout: 246 seconds] 08:37 -!- raucao [~raucao@skippe2.nine.ch] has joined #c-lightning 09:40 < ctrlbreak> anyone alive in here? 09:43 < ctrlbreak> Ok... ima see if I can open the lightningd.sqlite3 db in some form of explorer... HeidiSQL maybe. 09:53 < ctrlbreak> Yuk... I guess no support in Heidi yet, which is a bummer as I love it. I'm going to bug the dev to take my satoshis 10:43 < ctrlbreak> ... wheee; I'm all up in the DB guts. 11:13 < ctrlbreak> Hmm... I see my issue from last night. Going to restart lightningd with a considerable --rescan to see if it self corrects. 11:13 -!- kexkey [~kexkey@139.28.218.6] has joined #c-lightning 11:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 12:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 12:01 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 13:56 < m-schmoock> ctrlbreak: hell of a LN node you operate, like 60 channels i saw. Are you working on stuff like routing or channel optimization? 13:59 < m-schmoock> I wonder what folks like aphito.com (02809e936f0e82dfce13bcc47c77112db068f569e1db29e7bf98bcdd68b838ee84) with 900+ channels use, LND or c-lightning. Why the hell that much channels and stake anyway? 14:01 < m-schmoock> try to make a living on LN fees :D 14:23 < molz> they're crazy 14:23 < m-schmoock> trying to make a living on LN fees, until they realize that hackers make a living on them ;) 14:26 < molz> yea or their disk fries 14:27 < m-schmoock> :D 14:59 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 15:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:08 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:09 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 15:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 15:17 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 16:22 < ctrlbreak> Okay... So I'm ragey as f^%# tonight. I've been moving all my mobile phone stuff over to my new S10 from a 5yo OnePlus One... and trying to run eclair, and connect to my own ElectrumX node. 16:22 < ctrlbreak> requires SSL. Have my own self-signed cert on it. No biggie... import into certificate store on Android, still no cigar. 16:24 < ctrlbreak> Turns out things were changed in Android a few versions back and now it may not be enough to get a self-signed certificate in the *User* store on the device. If the app isn't compiled to also allow CAs from the User store, it'll *only* trust those in the System store. 16:24 < ctrlbreak> Grrrrrrrr. 16:26 -!- SnowGoose [b00af8c8@gateway/web/freenode/ip.176.10.248.200] has joined #c-lightning 16:29 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:30 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 16:30 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 16:38 < grubles> why not use spark? 16:39 < ctrlbreak> m-schmoock: Yes. I'm *trying* to be a conscientious node operator and will TRY to keep my channels balanced, but I have less time than previously to put towards it. I wanted to experiment with setting some 'interesting' fee rates on a per-channel basis to try and get things to balance themselves organically (maintained via script)... 16:39 < ctrlbreak> ... and I may actually get around to it one day! 16:39 < ctrlbreak> Hmmm.. Spark... tell me more ;-) 16:41 < ctrlbreak> woot... my big-ass --rescan appears to have fixed my broken "unconfirmed" txid. 16:41 < grubles> actually it might run into the same issue 16:41 < grubles> but you can run it over tor 16:41 < grubles> and the server-side component can be run as a hidden service 16:43 < ctrlbreak> hmmm... I should probably check it out. 16:44 < ctrlbreak> I need to get my 'crypto' VMs moved out to one of the perimeter DMZs and given a common Tor proxy in addition to clearnet. 16:46 < SnowGoose> Hey. Im trying to run c-lightning on my VM, while rpc remoting to my bitcoin core full node running on the host machine.. I seem to get this error when i try to run lightningd even though i configured everything: 16:46 < SnowGoose> Wallet blockchain hash does not match network blockchain hash: 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 != 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f. Are you on the right network? (--network={bitcoin, testnet, regtest, litecoin or litecoin-testnet}) lightningd: Wallet network check failed. 16:46 < ctrlbreak> Hmmm... that's an interesting one. 16:47 < ctrlbreak> You are trying to be on testnet, or mainnet? 16:47 < SnowGoose> Both my lightningd conf file and the bitcoin.conf running on the host machine specify mainnet, so i dont think thats the problem.. More like, its not connecting properly? 16:48 < ctrlbreak> hmmm... I have mine stacked on the same node... let me review my confs and see if I notice anything? 16:48 < SnowGoose> Sure! 16:49 < ctrlbreak> Hmmm.. you didn't have a bitcoind running on the VM at any point, did you? 16:50 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds] 16:50 < SnowGoose> At first i didnt, but after days of this message i did try installing bitcoind on the VM as well.. but it didnt help 16:50 < ctrlbreak> has it since been removed from the VM? 16:51 < SnowGoose> Its still installed, but not running 16:51 < ctrlbreak> hmm... kk. 16:52 < SnowGoose> My host machine runs windows and virtualbox. I set up a VM running debian and a host only network between them. On this network the host has ip (66.66.66.11 and the VM has 66.66.66.101) 16:52 < grubles> SnowGoose: it's probably because you ran lightningd on testnet first 16:52 < grubles> ie. without --mainnet 16:52 < SnowGoose> Hm yeah, its possible. The first time i started it, i had probably not found the config file yet 16:52 < ctrlbreak> I don't have _anything_ in my CL config explicitly telling it to look to localhost for bitcoind either... I wonder how mine is even working. lol. 16:53 < SnowGoose> Probably thats default 16:53 < grubles> try --help 16:53 < grubles> should list all the defaults 16:53 < SnowGoose> So, how can i "purge" it, if it still has some data from starting in testnet mode? 16:56 < ctrlbreak> SnowGoose : You have all these defined and pointing to your host machine, correct? 16:56 < ctrlbreak> --bitcoin-rpcuser bitcoind RPC username 16:56 < ctrlbreak> --bitcoin-rpcpassword bitcoind RPC password 16:56 < ctrlbreak> --bitcoin-rpcconnect bitcoind RPC host to connect to 16:56 < ctrlbreak> --bitcoin-rpcport bitcoind RPC port 16:56 < SnowGoose> Yeah. user and pass are set in both machines corresponding config files 16:56 < SnowGoose> lightning conf: bitcoin-rpcconnect=66.66.66.11 bitcoin-rpcport=8332 network=bitcoi 16:56 < SnowGoose> n 16:57 < ctrlbreak> ... and just as important, on the host, bitcoind is actually BOUND TO and listening on that VMNET address? (Unless your guest and host are both bridged and on the same subnet) 16:57 < SnowGoose> bitcoin.conf: rpcport=8332 rpcallowip=127.0.0.1 rpcallowip=66.66.66.101 16:58 < SnowGoose> i tried different combinations of rpcallow ip, rpcallowip+rpcbind since i didnt really understand the difference, but so far nothing makes a difference 16:58 < ctrlbreak> What is the host OS? 16:58 < SnowGoose> win 10 16:58 < ctrlbreak> Use resource monitor to check the listening ports on the network tab. 16:59 < ctrlbreak> see if the host bitcoin is actually bound to the desired ip:ports 17:00 < SnowGoose> Listening ports: bitcoin-qt.exe port 8333 and 8332, tcp, not restricted 17:01 < ctrlbreak> and under address? 17:01 < ctrlbreak> loopback? IPv4 unspecified ? 17:01 < SnowGoose> 8333 loopback, 8332 ipv4 unspecified 17:02 < ctrlbreak> hmmm.. k. 17:02 < SnowGoose> is it correct? 17:03 < SnowGoose> running bitcoin core through tor which might explain loopback i dunno.. its working for sure 17:03 < ctrlbreak> I believe so. If your host has an IP of 66.66.66.11 (very strange IP, btw) it should be bound to it. 17:03 < ctrlbreak> What's the IP of the VM in this case? 17:04 < SnowGoose> 66.66.66.101 17:04 < SnowGoose> these is their ip-addresses on the host-only network that i set up in virtualbox, i just picked something 17:05 < SnowGoose> should behave like a lan if i understand it correctly. I can ping fine between them and currently sshing to the VM from host machine 17:05 < ctrlbreak> and you can otherwise communicate between the two via those IPs? e.g. you can ping 66.66.66.11 from... 17:05 < ctrlbreak> kk... I'll assume layer3 is working fine then. 17:06 < SnowGoose> If grubles is right, and the problem is that i ran lightningd in testnet mode at some point, can i purge it? should i reinstall? 17:06 < SnowGoose> or just remove some .db files or something 17:06 < ctrlbreak> Hmmm, I'm not sure. 17:06 < ctrlbreak> lol... make a backup folder and move stuff? 17:07 < ctrlbreak> hsm_secret, lightningd.sqlite3, gossip_store. 17:07 < ctrlbreak> I'd try moving them to a backup folder and then restarting lightningd to see if it 'starts fresh' on mainnet 17:08 < SnowGoose> Alright sounds like its worth a shot. where is gossip_store? i found the other two 17:10 < ctrlbreak> ahh... no worries then. might not have been created yet? 17:19 < SnowGoose> Yeah. Looks like this is it! Its doing.. stuff.. now. 17:26 < SnowGoose> Thank you gentlemen! 17:51 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 17:55 < molz> SnowGoose, ! 17:58 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds] 18:00 < molz> SnowGoose, if you don't have any btc in the new node, you can delete the whole .lightning datadir and start fresh 18:17 < SnowGoose> Yeah got nothing to loose in this one yet. 18:18 < SnowGoose> So you are here too! 18:21 < molz> lol 18:21 < molz> SnowGoose, how do you get c-lightning to connect to your bitcoind? 18:21 < molz> which is not on the VM 18:22 < SnowGoose> I set up a host-only network between host and vm 18:23 < SnowGoose> so they can ping, ssh etcetera, they are on the same subnet.. after that just configure the rcp parameters correctly in both config files 18:24 < molz> i see 18:25 < molz> in that case i'm guessing if you have WSL installed you can get clightning to connect to your bitcoind on native windows 18:26 < SnowGoose> my host is running native windows 18:26 < SnowGoose> the vm running debian 18:27 < molz> do you have WSL? 18:27 < SnowGoose> nope 18:27 < molz> i like WSL 18:27 < molz> compiling bitcoin on wsl right now as we're chatting 18:28 < molz> bitcoin for windows 18:40 < SnowGoose> cool maybe i'll check it out 18:40 < SnowGoose> Next step for me is to try and connect a spark wallet running on my host, to the clightning instance running in the vm 18:43 < molz> spark seems complicated 18:43 < SnowGoose> I wanna try it. 18:43 < ctrlbreak> I'm about to *repackage* the Eclair wallet apk so I can use my own certificate with my electrum server O.o 18:43 < ctrlbreak> lol 18:50 < molz> wow ctrlbreak :D 18:52 < molz> "When the Cordova app is first run, the user must first pair their device with the remotely-accessible Spark server. A quick way to do this is to run Spark with -Q," <-- how? 19:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 19:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:19 -!- Madcapslaugh_ [8de20f7f@gateway/web/freenode/ip.141.226.15.127] has quit [Ping timeout: 256 seconds] --- Log closed Sun Mar 17 00:00:18 2019