--- Log opened Wed Jul 08 00:00:13 2020 01:55 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 02:08 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 02:52 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has joined #c-lightning 02:52 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has joined #c-lightning 02:57 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has quit [Ping timeout: 256 seconds] 02:58 -!- jonatack [~jon@213.152.162.5] has joined #c-lightning 03:52 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 03:52 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 04:00 -!- shupfel [~Bohphah3@92.117.137.22] has joined #c-lightning 04:03 < shupfel> Hi. Has s/o an idea? Problem: I've a running / working clightning-node. Sent some - additional - funds to it on-chain. The on-chain transaction was successfull, has 6 confirmations now, but lightning-cli listfunds still shows the old value. 04:03 < shupfel> [ yes, I re-used an address, I know this is bad practice ] 04:04 < zmnscpxj__> Hmm what does getinfo show? 04:04 < zmnscpxj__> particularly "blockheight" 04:05 < shupfel> 638281 04:06 < zmnscpxj__> which matches my blockheight, hmmmmmmmm 04:07 < shupfel> bitcoin-cli gettxout also shows the current value 04:07 < shupfel> are 6 confirmations sufficient? 04:09 < zmnscpxj__> 1 should be... 04:10 < zmnscpxj__> can you double-check listaddrs output? 04:10 < zmnscpxj__> ah, that is a dev command 04:10 < zmnscpxj__> dev-listaddrs 04:16 < shupfel> hmm dev-listaddrs gives me a list of 30 addresses, bech32 and p2sh 04:16 < zmnscpxj__> And the address you sent to is amongst them? 04:16 < shupfel> but the address with the 'missing' funds is not in this list 04:17 < shupfel> no 04:17 < zmnscpxj__> well, then are you sure the address is for *that* node? 04:17 < shupfel> 'listfunds' shows it - so... 04:17 < zmnscpxj__> what does its entry look like? 04:17 < zmnscpxj__> in listfunds? 04:18 < shupfel> { 04:18 < shupfel> "outputs": [ 04:18 < shupfel> { 04:18 < shupfel> "txid": "c12c75077bb0c5db4f25467b0e1097322840ba7d47f97dbfdd585562c23a1638", 04:18 < shupfel> "output": 0, 04:18 < shupfel> "value": 64209, 04:18 < shupfel> "amount_msat": "64209000msat", 04:19 < shupfel> "address": "bc1qvr94k4l7ktesvg74kn759w34mdzmrt07hpgfnm", 04:19 < shupfel> "status": "confirmed", 04:19 < shupfel> "blockheight": 630894 04:19 < shupfel> }, 04:19 < zmnscpxj__> okay, lemme study the code a little more 04:20 < zmnscpxj__> The address bc1qvr94k4l7ktesvg74kn759w34mdzmrt07hpgfnm was from newaddr or not? 04:20 < shupfel> no, it wasn't 04:20 < zmnscpxj__> was it change? 04:20 < zmnscpxj__> I am unsure if we track change 04:20 < shupfel> ohm. good question 04:20 < shupfel> could be 04:21 < shupfel> i've as second 'output' in listfunds , this one also appears in dev-listaddrs 04:23 < shupfel> i'm using "version": "0.8.1", BTW 04:26 < zmnscpxj__> lemme dig the code first 04:37 < zmnscpxj__> no, change outputs and normal outputs should be the same..... 04:38 < zmnscpxj__> worst comes to worst, you have to do dev-rescan-outputs, and wait a long time for the rescan to finish 04:38 < zmnscpxj__> and avoid doing any onchain activity 04:41 < zmnscpxj__> hmm, though we do not add change addresses to the txfilter, I think 04:41 < zmnscpxj__> so if the address is a change address, it might be because of that 04:42 < shupfel> started dev-rescan-outpus, returns a liast of txid and exits. 04:42 < zmnscpxj__> is your money now in listfunds? 04:42 < shupfel> no :( 04:43 < zmnscpxj__> crikey crikey 04:43 < shupfel> maybe i should close all channels and recover from seed.... 04:43 < shupfel> and never ever NOT use newaddr again :-| 04:43 < zmnscpxj__> hold off on that, presumably if it is in listfunds, we have the ability to at least spend from it 04:45 < shupfel> I could try to open a channel with funds > previous_funds > current_funds 04:45 < shupfel> sorry, current > newchannel-fund > previous-funds 04:49 < zmnscpxj__> Okay, so it *looks* like the address is a change address, and we do not put change addresses in our txfilter 04:49 < zmnscpxj__> which means if a new block comes with that address, we do not notice it. 04:49 < zmnscpxj__> I think 04:49 < zmnscpxj__> hmmmmmmmmmmmmm 04:52 < zmnscpxj__> Or you know what? we reinitialize the txfilter on startup, and we do not differentiate between change and normal addresses at startup 04:52 < zmnscpxj__> so you could try just stopping the daemon for now 04:53 < zmnscpxj__> And restart with the --rescan 100 argument 04:53 < shupfel> BTW, fundchannel ussing the new funds fails, as expected 04:53 < shupfel> ok, stopping... 04:53 < zmnscpxj__> since the money you are missing is less than a dozen blocks confirmed anyway 04:54 < shupfel> so, "lightningd --rescan 100", right? 04:54 < zmnscpxj__> plus your other arguments that you use 04:54 < zmnscpxj__> 100 should be safe 04:54 < zmnscpxj__> would take a bit on startup but well 04:55 < zmnscpxj__> the money is not confirmed for more than a dozen blocks so you could get away with --rescan 12 or 20 but just do 100 to be safe 04:55 < shupfel> ok, lightningd consuming lots of cpu, seems to work... ;) 04:55 < zmnscpxj__> we hope 04:55 < zmnscpxj__> when the cpu drops, try listfunds again 04:58 < shupfel> :( i'll retry with rescen=8000, which includes the first block the address was used 04:59 < zmnscpxj__> haha, okay 04:59 < zmnscpxj__> better safe than sorry right? 05:00 < shupfel> 100 didn't work 05:00 < zmnscpxj__> noooooooooooooooooooo 05:00 < zmnscpxj__> sorry, out of ideas 05:01 < shupfel> thank you so much for your support! 05:01 < zmnscpxj__> np, hope you get better support elsewhere 05:01 < shupfel> I'll keep experimenting and report later. 05:02 < shupfel> seems i found an interesting 'lack of feature' ;-) 05:02 < shupfel> lightningd still scanning 05:06 < zmnscpxj__> *cough* not a bug, it prevents users from accidentally reusing address *cough* LOL 05:07 < shupfel> yees, THIS lesson i learned. 05:07 < zmnscpxj__> sorry 05:07 < shupfel> thought "i'm such a pro, don't need to follow recomendations" 05:07 < zmnscpxj__> looks like a quick fix on our end would be to add change outputs to txfilter 05:07 < shupfel> :-D 05:07 < zmnscpxj__> hahah 05:08 < shupfel> of course a fix would be very nice :-) 06:17 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 06:23 -!- jonatack [~jon@213.152.162.5] has quit [Ping timeout: 256 seconds] 06:42 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:46 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Quit: ZNC 1.7.4+deb7 - https://znc.in] 06:47 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #c-lightning 07:18 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds] 07:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 07:36 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 07:48 -!- vincenzopalazzo [~vincent@153.33.4.26] has joined #c-lightning 07:51 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 07:52 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds] 07:53 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #c-lightning 07:53 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 08:30 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 08:34 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 08:34 -!- vasild_ is now known as vasild 08:57 -!- vincenzopalazzo [~vincent@153.33.4.26] has quit [Quit: Leaving] 09:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 09:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 09:08 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 09:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 09:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:31 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Remote host closed the connection] 09:33 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 09:38 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Ping timeout: 256 seconds] 09:41 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 09:49 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 10:02 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 10:31 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 10:56 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 10:59 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds] 11:45 -!- vincenzopalazzo [~vincent@153.33.4.26] has joined #c-lightning 11:51 -!- MasterdonX [~masterdon@185.246.211.104] has quit [Quit: ZNC 1.7.5 - https://znc.in] 11:51 -!- MasterdonX [~masterdon@185.246.211.104] has joined #c-lightning 12:17 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 240 seconds] 12:29 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-siipwwkhxjcfolyk] has joined #c-lightning 12:37 -!- felixweis [sid154231@gateway/web/irccloud.com/x-rwtspefaioxloplv] has joined #c-lightning 12:43 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 258 seconds] 12:54 -!- bitauger [sid371414@gateway/web/irccloud.com/x-srmncbubjrowmfwg] has joined #c-lightning 13:07 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning 13:28 -!- fjahr [sid374480@gateway/web/irccloud.com/x-uivuzkqvxqkxtfmn] has joined #c-lightning 13:31 -!- Letze [sid63391@gateway/web/irccloud.com/x-oajlgkrsjjigdypd] has joined #c-lightning 13:37 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Remote host closed the connection] 13:44 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 15:18 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Remote host closed the connection] 15:45 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 15:50 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Ping timeout: 256 seconds] 15:50 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 16:11 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:51 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 16:56 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 260 seconds] 17:07 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 17:08 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning 17:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:28 -!- shupfel [~Bohphah3@92.117.137.22] has quit [Ping timeout: 240 seconds] 17:32 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 17:37 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 264 seconds] 17:53 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds] 17:57 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 18:00 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 18:11 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 19:01 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection] 20:21 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 20:22 -!- dr-orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has quit [Read error: Connection reset by peer] 20:23 -!- dr_orlovsky [~dr-orlovs@xdsl-188-154-184-23.adslplus.ch] has joined #c-lightning 20:26 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has quit [Ping timeout: 264 seconds] 20:30 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 20:33 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 20:33 -!- vasild_ is now known as vasild 20:53 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 260 seconds] 20:53 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning 22:05 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning 22:06 -!- Amperture [~amp@65.79.129.113] has quit [Client Quit] 22:25 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 22:34 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 22:35 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 22:36 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 22:46 -!- Barno [~Barno@93-34-214-192.ip51.fastwebnet.it] has joined #c-lightning 23:21 -!- vincenzopalazzo [~vincent@153.33.4.26] has quit [Remote host closed the connection] 23:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] --- Log closed Thu Jul 09 00:00:13 2020