--- Log opened Thu Mar 07 00:00:08 2019
00:39 -!- pseudozach___ [4eace84f@gateway/web/freenode/ip.78.172.232.79] has joined #c-lightning
00:39 < pseudozach___> hello, is this the right place to ask a question about my c-lightning node? I seem to be missing funds after channel closure...
00:40 < pseudozach___> or should I open an issue? 
00:45 < m-schmoock> pseudozach___: normally you need to wait a 144 block timeout and the funds will reappear in yout `litsfunds` outputs
00:46 < m-schmoock> I had this. You can check for it int the `listpeers` log entries of the relevant channel that got closed (by force). It should have one peer where it says waiting for 144 blocks or somthing
00:46 < pseudozach___> I did wait that much, listpeers showed me that.
00:46 < pseudozach___> yes, and then the funds were split and sent, that transaction also happened 144 blocks ago -> https://blockchair.com/bitcoin/transaction/3d737f1d1a604c36d393cecc6f7eb14c4d97a7b83c36dcccc71f3816a075daed
00:46 < m-schmoock> pseudozach___: yes, I also had this. in this case you need to restart the daemon and wait for yet another 144 blocks :/
00:47 < m-schmoock> hmmm
00:47 < pseudozach___> listfunds still do not show the funds. also dev-list-addr do not show me this address either
00:47 < pseudozach___> that's the strange part.
00:47 < m-schmoock> i see
00:47 < m-schmoock> how was the channel closed? unilaterally or with consent?
00:47 < pseudozach___> address seem to be a bit short in length, I dont know if that's expected...
00:47 < pseudozach___> the other party closed it
00:48 < m-schmoock> by force?
00:48 < pseudozach___> unilaterally
00:48 < m-schmoock> kk
00:48 < m-schmoock> can you pastebin the listpeers output for that node?
00:48 < pseudozach___> sure
00:49 < m-schmoock> lol, its just about 144 confirmations right now
00:49 < m-schmoock> with luck you will see the funds in a couple of minutes or now already
00:49 < m-schmoock> okay i think I know what happened
00:50 < m-schmoock> is it the missing 0.01227821 BTC on your side
00:50 < m-schmoock> ?
00:51 < pseudozach___> 0.177 is my side
00:51 < pseudozach___> 0.0177
00:52 < m-schmoock> hm
00:52 < pseudozach___> I thought 144 blocks were from the channel closing time, that's 288 block until it's spendable. do I get that right?
00:52 < pseudozach___> sorry pastebin is blocked so it took me a while:
00:52 < pseudozach___> https://pastebin.com/WUF5mvKj
00:52 < m-schmoock> so this is supposedly your address: bc1qlswkmthqv2k2vvf8nad0txe8mrh6dcg5vw8mvm 
00:52 < pseudozach___> before and after listpeers
00:52 < pseudozach___> yes
00:52 < m-schmoock> and you cant find it in the addresses
00:52 < pseudozach___> nope
00:52 < m-schmoock> kinda sucks bro :/
00:53 < m-schmoock> going through the logs...
00:53 < pseudozach___> certainly does :)
00:53 < pseudozach___> I got channels to open ;)
00:53 < m-schmoock> we will figure it out, maybe with some additional help as Im rather newb as well
00:53 < pseudozach___> cool, yeah let me know, I can provide info and I know the other party as well, opennode's lnd node.
00:54 < m-schmoock> need a coffee and have a telco before I can get into it
00:54 < m-schmoock> "brb"
00:54 < pseudozach___> k
00:55 < m-schmoock> in the meantime you can try restart the daemon and paste another listpeers and check outputs
00:55 < m-schmoock> I had something similar once where a subdaemon died
00:55 < m-schmoock> and funds didnt unlock properly
00:56 < pseudozach___> daemon already crashed a few times since, so it has already restarted
00:56 < pseudozach___> btw, I kept getting owning daemon died errors while trying to open another channel throughout yesterday
00:56 < pseudozach___> I'm on 0.7.0
00:57 < pseudozach___> I saw a few related issues on github but I dont want to run anything without understanding
01:31 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit []
01:31 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning
01:33 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
01:53 < m-schmoock> pseudozach___: your pastebin included the following log in the "BEFORE" block: "            "ONCHAIN:All outputs resolved: waiting 29 more blocks before forgetting channel"
01:54 < m-schmoock> have these 29 blocks been found yet? (meaning is this log output older than 29 blocks)
01:54 < pseudozach___> yes, that was from before.
01:55 < pseudozach___> the current listpeers is the one below, channel is forgotten already
01:55 < m-schmoock> so and now it just hangs in "Funding transaction locked. Waiting for their announcement signatures" which is incorrect?
01:55 < m-schmoock> ah ok
01:55 < m-schmoock> its a differen peer is see
01:55 < pseudozach___> yep
01:57 < m-schmoock> and have you restarted since you experienced the missing
01:57 < m-schmoock> otuptu ?
01:57 < m-schmoock> lol
01:57 < m-schmoock> output
01:57 < pseudozach___> yes I restarted bunch of times, changed ip etc.
01:58 < m-schmoock> hmm
01:58 < pseudozach___> I saw a ticket about how unilaterally closed channels are tracked differently and these addresses are derived directly or something. could it be related?
01:59 < pseudozach___> should I do a rescan?
01:59 < m-schmoock> play
01:59 < m-schmoock> okay
01:59 < m-schmoock> god damn, my keyboard sucks
01:59 < pseudozach___> these addresses are *not* derived
01:59 < m-schmoock> dev-listaddrs can be used with a higher derivation number
01:59 < m-schmoock> thats one try
01:59 < m-schmoock> a rescan is always safe.... so rusty said to me once
02:00 < m-schmoock> i would try it
02:00 < pseudozach___> ok and dev-listaddrs, how to list with higher derivation?
02:00 < m-schmoock> because it is a normal output and not some locking script state
02:00 < m-schmoock> just pass it as value
02:00 < pseudozach___> yeah it should just arrive if I own that private key somehow
02:00 < pseudozach___> what number should I put?
02:00 < m-schmoock> quote "dev-listaddrs - Show addresses list up to derivation {index} (default is the last bip32 index)"
02:01 < m-schmoock> its numerical starting from 0 or 1
02:01 < m-schmoock> and goes as fas aas many addresses you generated
02:01 < m-schmoock> basically thats what the rescan does
02:01 < m-schmoock> it checks the blockchain for outputs on your addresses
02:01 < m-schmoock> :]
02:01 < pseudozach___> so that wont help...
02:02 < m-schmoock> it would
02:02 < m-schmoock> because it tries higher indexes
02:02 -!- kexkey [~kexkey@68.168.122.228] has quit [Read error: Connection reset by peer]
02:02 < m-schmoock> thats the point
02:02 < m-schmoock> just do the rescan
02:03 < m-schmoock> if your unsure, you can increase the derivation index by hand in the listaddrs and check if your missing funds address comes up eventually
02:04 < m-schmoock> because thats exactly what rescan does additionally to ascing the bitcoind if theres output on these addresses
02:04 < m-schmoock> your lightning did miss a output for unknown reason, maybe some subdaemon died issue
02:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:21 < m-schmoock> ctrlbreak: thanks, just try and see where and how far you get. My motivation is that I'm so totally pissed off by the status quo: Fiat, banks, politics, and even Onchain 'scaling' propaganda, ... wars, environmetnal impacts of the need for unlimited growth to pay for fiat interest rates from unborn children... The list is really long. I think that its the best for us all if we focus our brain 
02:21 < m-schmoock> output on solutions instead of doing an otherwise meaningless boring job like the other billion people.
02:22 < pseudozach___> ok I'll run rescan
02:22 < m-schmoock> -QQQQ°_°   (a worm)
02:22 < m-schmoock> pseudozach___: tell me if it worked or not
02:23 < pseudozach___> and it magically appears! wow awesome
02:23 < pseudozach___> thank you so much man
02:24 < pseudozach___> really appreciated!
02:27 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
02:34 < m-schmoock> glad we found the funds in the void :>
02:35 < m-schmoock> we may think about having a rescan on daemon startup anyway, so we get less of this troubles until we fixed all the glitches in the subdaemons
02:38 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:41 < pseudozach___> I support that, I should have done rescan earlier but I guess I wanted to check first. 
02:59 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
03:04 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
03:31 -!- pseudozach___ [4eace84f@gateway/web/freenode/ip.78.172.232.79] has quit [Quit: Page closed]
04:10 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning
04:31 < t0mix> hey, pseudozach___ =) nice to see you around
04:40 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has quit [Ping timeout: 245 seconds]
04:45 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has joined #c-lightning
05:06 < molz> m-schmoock, how do you run the rescan?
05:06 < molz> `lightning-cli rescan` ?
05:10 < m-schmoock> molz:   ./configure --enable-developer   ; make -j10  ; ./cli/lightning-cli dev-rescan-outputs
05:10 < m-schmoock> :]
05:10 < m-schmoock> its a developer command
05:51 < molz> ah dev-rescan-outputs
05:52 < molz> m-schmoock, i've always compiled with ./configure --enable-developer
06:02 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:26 < rafalcpp> if anyone is interested in reddit, then there is missconception that LN routing is NP hard, being again pushed on bcash subforum "/r/btc".  Perhaps people might want to clarify what is complexity of that problem actually
07:40 < molz> m-schmoock, thank you :)
08:27 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
08:31 -!- kexkey [~kexkey@68.168.122.228] has joined #c-lightning
08:41 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection]
08:49 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
09:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
09:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
09:24 < m-schmoock> rafalcpp: i believe anybody has the right to be stupid and publish their opinion as long as the rest is allowed to behave otherwise :D
09:25 < m-schmoock> even if it 'would' be NP hard wouldnt mean we would not be able to find optimal 'engough' solutions
09:26 < m-schmoock> who cares for bcash anyway
09:32 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
10:07 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Remote host closed the connection]
12:23 -!- kexkey [~kexkey@68.168.122.228] has quit [Quit: Do, don't don't]
12:24 -!- kexkey [~kexkey@68.168.122.228] has joined #c-lightning
12:28 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
12:43 < t0mix> rafalcpp, my rpi can tell you goodnight stories about tortures I make on it, each time I issue 'getroute'. true stories.
13:06 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Quit: Leaving]
13:15 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
14:11 -!- Janaka-Steph [~Janaka-St@2001:8a0:6a57:ee01:8dbe:d3b:9a73:1716] has joined #c-lightning
14:11 < Janaka-Steph> Hello!
14:12 < Janaka-Steph> I can't find lightningd on Ubuntu
14:12 < Janaka-Steph> command not found, need to add a path, but which one? where is it mention in the doc?!
14:13 < Janaka-Steph> Do you have a slack? ^^
14:21 < Janaka-Steph> Oh god, the exec is generated in the repo itself! Alright!
14:25 < Janaka-Steph> So I need to move the whole repo to /usr/local/bin right?
14:26 < Janaka-Steph> just moving lightningd doesn't work 
14:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:38 < Janaka-Steph> Ok ok, `make install` is moving the executables 
14:39 < ctrlbreak> Slack is gross
14:39 < ctrlbreak> lol
14:40 < Janaka-Steph> So to let you know, the readme is incomplete
14:40 < Janaka-Steph> https://github.com/ElementsProject/lightning#installation
14:40 < Janaka-Steph> 'make install' is missing
14:41 < Janaka-Steph> ```
14:41 < Janaka-Steph> For the impatient here's the gist of it for Ubuntu and Debian:
14:41 < Janaka-Steph> sudo apt-get update
14:41 < Janaka-Steph> sudo apt-get install -y \
14:41 < Janaka-Steph>   autoconf automake build-essential git libtool libgmp-dev \
14:41 < Janaka-Steph>   libsqlite3-dev python python3 net-tools zlib1g-dev libsodium-dev
14:41 < Janaka-Steph> git clone https://github.com/ElementsProject/lightning.git
14:41 < Janaka-Steph> cd lightning
14:41 < Janaka-Steph> ./configure
14:41 < Janaka-Steph> make
14:41 < Janaka-Steph> ```
14:41 < Janaka-Steph> Well I was impatient.. and then wtf
14:43 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
14:50 < Janaka-Steph> And this is what I am doing https://github.com/bitcoin-studio/Bitcoin-VirtualMachine
14:50 < Janaka-Steph> I added c-lightning
14:51 < Janaka-Steph> Feel free to improve the Ansible playbooks!
14:52 -!- Janaka-Steph [~Janaka-St@2001:8a0:6a57:ee01:8dbe:d3b:9a73:1716] has quit []
15:03 < molz> ctrlbreak, pffft
15:51 -!- Janaka-Steph [~Janaka-St@2001:8a0:6a65:d400:11cc:7ba3:d762:f3a1] has joined #c-lightning
15:54 -!- Janaka-Steph [~Janaka-St@2001:8a0:6a65:d400:11cc:7ba3:d762:f3a1] has quit []
18:50 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:06 < grubles> if i were to migrate my c-lightning instance to another computer on a different cpu architecture, would there be any issues?
20:06 < grubles> i'm planning on migrating from ppc64le to arm64 
20:26 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
20:36 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
21:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 255 seconds]
22:54 -!- harding [~quassel@li1258-130.members.linode.com] has quit [Ping timeout: 245 seconds]
23:01 -!- harding [~quassel@li1258-130.members.linode.com] has joined #c-lightning
--- Log closed Fri Mar 08 00:00:10 2019