--- Log opened Sun Aug 22 00:00:45 2021
02:37 -!- undeath [~undeath@user/undeath] has joined #joinmarket
03:07 < JoinMarketRelay> [hackint/kristapsk] belcher, v0.9.1 should be announced on JM twitter
03:08 < belcher> ok will do
03:33 < belcher> ok tweeted
04:16 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.2]
05:12 -!- undeath [~undeath@user/undeath] has joined #joinmarket
05:18 -!- JMBridged [~CoinJoins@gateway/tor-sasl/jmbridge] has joined #joinmarket
05:20 -!- JMBridge [~CoinJoins@gateway/tor-sasl/jmbridge] has quit [Ping timeout: 244 seconds]
05:20 -!- JMBridged is now known as JMBridge
06:46 -!- hij [~hij@ip72-194-211-20.sb.sd.cox.net] has joined #joinmarket
06:49 < hij> I'm trying to add fidelity bonds to my current wallet. I have recovered the wallet with fidelity bond set to yes and the addresses match but despite rescanning 4 times, it only finds two used addresses with some dust. Looking at my original wallet, I do not see an issue with a gap.
07:07 < waxwing> hij, can you try with --recoversync?
07:09 < hij> ok
07:11 < hij> bitcoin-qt --recoversync tells me invalid parameter
07:11 < waxwing> python wallet-tool.py walletname.jmdat --recoversync
07:11 < waxwing> on the new fb wallet
07:23 < hij> does this take a long time? I put it the command, the cursor blinked a few time and now is not blinking.
07:40 -!- NorrinRadd [~username@154.6.20.113] has quit [Ping timeout: 252 seconds]
08:10 < waxwing> uh .. i haven't heard of  behaviour like that (sorry was afk)
08:10 < waxwing> are you able to talk to bitcoind with bitcoin-cli (i.e. is rpc working OK?) because that's the first thing that comes to mind if it's just hanging
08:13 < hij> It completed and gave me the message about "Restart bitcoin core with -rescan". The wallet still only shows two used addresses with 547 sat balances.
08:15 < waxwing> how long did it take? and, i know this sounds dumb, but can you rerun that command again and see if anything changes?
08:15 < waxwing> (for obscure reasons there are situations where running it more than once actually "corrects" it)
08:16 < waxwing> there are other things you can do. run with -g 100 or some large number. also there is the "bitcoin-rpc-no-history" option (i forget exact syntax)
08:16 < hij> I already started. It still looks like it is hanging but I'll let it run a long time again since it eventually came back to the command line
08:17 < waxwing> that aspect of what you're seeing is a bit dubious, but .. difficult to say.
08:17 < waxwing> this is from the default config: "# When using bitcoin-rpc-no-history remember to increase the gap limit to scan for more addresses, try -g 5000"
08:18 < waxwing> if you do that it's intended to be kinda "guaranteed 100%" to find all funds in case of a large wallet with big gaps, but it takes a while.
08:18 < hij> FYI, bitcoin-cli getblockcount worked so the rpc is working
08:18 < waxwing> "large" means lots of indexes used up in the wallet here, of course.
08:20 < hij> just to be clear , I would use python wallet-tool.py walletname.jmdat -g 5000?
08:20 < waxwing> if you want bitcoin-rpc-no-history you have to put it in the config
08:21 < waxwing> i think there's a brief description somewhere, probably in USAGE.md
08:22 < waxwing> https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/8c57852b2ae3c5a6ca0ec39724495d391982cfc2/docs/release-notes/release-notes-0.6.2.md#no-history-wallet-synchronization
08:23 < waxwing> only found it in release notes, huh
08:25 < hij> But if I do the no history recovery, from looking at the page you just linked, it looks like I could not use it as a maker since it would not generate new addresses
08:52 < waxwing> yes
08:53 < waxwing> i personally woudl be using something like python wallet-tool.py walletname.jmdat -g 500 --recoversync. i think 5000 is overkill.
08:53 < waxwing> and as mentioned, paying attention to whether there is change from one run to the next.
08:54 < waxwing> but there are details of circumstance that i don't know, is the wallet very heavily used or not, are you recovering on the same Core instance as you ran it before, maybe some other things.
09:21 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.2]
09:31 < hij> I will try with -g 500. The wallet has been used a lot and I am recovering on the same core instance.
09:36 < hij> success! Thanks
10:16 < waxwing> hij, no worries, good
14:31 -!- NorrinRadd [~username@154.6.20.210] has joined #joinmarket
18:22 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
18:34 -!- belcher [~belcher@user/belcher] has joined #joinmarket
21:05 -!- hij [~hij@ip72-194-211-20.sb.sd.cox.net] has quit [Quit: Connection closed]
21:11 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
21:45 -!- dr_orlovsky [~dr-orlovs@31.14.40.18] has joined #joinmarket
21:45 -!- Michail [~Michail@michail.com] has joined #joinmarket
21:45 -!- Netsplit *.net <-> *.split quits: dr-orlovsky, Michail1
21:45 -!- Michail is now known as Michail1
21:48 -!- Netsplit *.net <-> *.split quits: takinbo
21:49 -!- Netsplit over, joins: takinbo
23:10 -!- dr_orlovsky [~dr-orlovs@31.14.40.18] has quit [Quit: ZNC 1.8.0 - https://znc.in]
--- Log closed Mon Aug 23 00:00:46 2021