--- Log opened Sun Sep 06 00:00:12 2020 00:27 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket 00:30 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 01:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds] 01:11 -!- belcher_ is now known as belcher 01:57 -!- jonatack [~jon@213.152.162.170] has joined #joinmarket 01:59 -!- cbeams_ [~cbeams@unaffiliated/cbeams] has joined #joinmarket 02:02 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Ping timeout: 240 seconds] 02:04 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #joinmarket 02:05 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer] 02:57 -!- waxwing_ [~waxwing@81-178-154-246.dsl.pipex.com] has joined #joinmarket 02:59 -!- waxwing [~waxwing@unaffiliated/waxwing] has quit [Ping timeout: 240 seconds] 03:17 -!- Antwon8Breitenbe [~Antwon8Br@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection] 03:20 -!- Tom61Sporer [~Tom61Spor@static.57.1.216.95.clients.your-server.de] has joined #joinmarket 03:33 -!- tralfaz [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket 03:34 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 03:53 -!- waxwing_ is now known as waxwing 03:53 -!- waxwing [~waxwing@81-178-154-246.dsl.pipex.com] has quit [Changing host] 03:53 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #joinmarket 03:58 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 240 seconds] 04:11 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 240 seconds] 04:40 < cbeams_> > waxwing: cbeams_, what was the version you were using before 0.20.0? 04:40 < cbeams_> 0.19.1 04:46 < cbeams_> > waxwing: and did you have `-deprecatedrpc=accounts` specified? 04:46 < cbeams_> I did not. 04:46 < cbeams_> > waxwing: cbeams_ you would find that `getaddressesbylabel` rpc with argument of "joinmarket-notify" will show that /132 address. 04:48 < cbeams_> Firstly, I have no idea what the address associated with /132 is, because, /132 is missing in every case, with --recoversync and without. It's /133 that shows up with --recoversync and does not without it. And the balance on the address associated with /133 accounts completely for the discrepancy between my current and historical balances. So I'm not concerned with /132. 04:49 < cbeams_> Second, I did run `getaddressesbylabel joinmarket-notify` and the results return three bech32 addresses, which surprised me since JoinMarket doesn't use these. In any case, I can't tell whether those results are "interesting" or not. 04:52 < cbeams_> > waxwing: cbeams_, if you have a chance could you try the following : `bitcoin-cli listaddressgroupings` 04:52 < cbeams_> I did this, and here's where I think something *does* get interesting... 04:53 < cbeams_> Let's go back to the listing I posted above. When I run with --recoversync and no-history enabled, I get results like the following from `display`: 04:54 < cbeams_> (again, actual addresses amounts are scrubbed here) 04:54 < cbeams_> m/49'/0'/1'/1/130 3000... 0.04200000 used 04:54 < cbeams_> m/49'/0'/1'/1/131 3001... 0.00420000 used 04:54 < cbeams_> m/49'/0'/1'/1/133 3003... 0.01112222 used 04:54 < cbeams_> m/49'/0'/1'/1/134 3004... 0.00042000 used 04:54 < cbeams_> m/49'/0'/1'/1/135 3005... 0.00004200 used 04:55 < cbeams_> we know /133 is the one that shows up only with --recoversync, and I've abbreviated its address here to read `3003...` 04:57 < cbeams_> Here's what I get from `listaddressgroupings`: 04:57 < cbeams_> $ bitcoin-cli listaddressgroupings | grep -B2 -A4 3003... 04:57 < cbeams_> [ 04:57 < cbeams_> [ 04:57 < cbeams_> "3003...", 04:57 < cbeams_> 0.00000000, 04:57 < cbeams_> "joinmarket-wallet-96b4d5" 04:57 < cbeams_> ] 04:57 < cbeams_> ], 04:58 < cbeams_> The amount displayed is 0, but as per the listing as above, we know the actual balance on address `3003...` is 0.01112222. And this can be verified in any block explorer. 04:58 < cbeams_> If we take a look at one of the adjacent addresses in the same way, say `3004...` above, `listaddressgroupings` shows the correct amount: 04:59 < cbeams_> $ bitcoin-cli listaddressgroupings | grep -B2 -A4 3003... 04:59 < cbeams_> [ 04:59 < cbeams_> [ 04:59 < cbeams_> "3004...", 04:59 < cbeams_> 0.00042000, 04:59 < cbeams_> "joinmarket-wallet-96b4d5" 04:59 < cbeams_> ] 04:59 < cbeams_> ], 05:00 < cbeams_> This certainly seems like a clue. 05:03 -!- jonatack [~jon@213.152.162.170] has quit [Quit: jonatack] 05:04 < cbeams_> whoa: I just re-ran `summary`, `history` and co without no-history and without --recoversync and my balance is back to where it should be! No more discrepancy, no more BUG ERROR, etc. 05:04 < cbeams_> And, seemingly un-coincidentally, the mempool has cleared out in the meantime between now and the last time I attempted these commands. 05:05 < cbeams_> I have no idea how this could have been a pending transaction problem after all the research we did above, and maybe it really is a coincidence. In any case, I'm pleasantly surprised. 05:12 < cbeams_> And another clue: My balance is now just slightly higher (double-digit sats) now than I expected it to be over the last few days while debugging this. I've had my yield generator turned off for at least the last 48 hours, so I know no new transactions should have been coming in. Is it possible that there was an outstanding join that completed in the meantime, bumping my balance up by this little amount, and somehow in the process reso 05:12 < cbeams_> lving this discrepancy? Unfortunately, I cannot consult JoinMarket `history` here to learn more, because as I explained earlier, my history stops in June (even though I've been running YG continuously). 05:22 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 06:35 -!- tralfaz is now known as Davterrra 07:00 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:b2d3:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 244 seconds] 07:06 < waxwing> ok sorry about 132/133 confusion :) reading. 07:07 < waxwing> the `joinmarket-notify` 3 bech32 addresses aren't too surprising; this label only gets used when a JM wallet pays out to an external address. (also note JM does have bech32 wallets, but that's a side story). 07:10 -!- Davterrra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 07:11 -!- Davterrra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket 07:14 < waxwing> i have a new theory about it (the theory i had earlier that it was to do with the *notify label is clearly wrong; the code already accounts for it, as i learned, except *possibly* some extremely obscure edge case which does not apply to you). 07:15 < waxwing> how about this: suppose that the utxo at '3003' was used as an input to a coinjoin, but with a low fee which sat in the mempool for a while. 07:15 < waxwing> then eventually for whatever reason that tx became invalid (someone didn't want to wait more and double spent a different input). 07:15 < waxwing> then it's possible (needs research) that the evidence you describe is consistent with that scenario. 07:16 < waxwing> meh. problem with that theory is, if it sat unconfirmed in mempool, your wallet-tool would report the balance at the new output. (it shows unconfirmed) 07:27 < waxwing> what type of transaction was it that funded '3003'? JM coinjoin or not? apart from any other clues, there is at least the question: if it is a JM coinjoin you participated in as maker, then there would be two outputs that got funded to your wallet rather than only one. 07:29 -!- rdymac [uid31665@gateway/web/irccloud.com/x-kyubrvrondtdyucn] has quit [Quit: Connection closed for inactivity] 07:44 -!- cbeams_ [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 07:59 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #joinmarket 08:02 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket 08:05 < cbeams> > waxwing: what type of transaction was it that funded '3003'? JM coinjoin or not? 08:06 < cbeams> there were ~10 inputs and ~20 outputs, so I assume a JM coinjoin. Certainly wasn't funded manually by me. 08:08 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 08:09 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #joinmarket 08:13 -!- fiatjaf [~fiatjaf@2804:7f2:2a83:c857:ea40:f2ff:fe85:d2dc] has joined #joinmarket 08:17 -!- rdymac [uid31665@gateway/web/irccloud.com/x-odsewlaeecrhdtzl] has joined #joinmarket 08:32 < waxwing> cbeams, gotcha. so ... it's just that one address with the weird behaviour, and not the other address of yours in that transaction? (I appreciate the answer might not be immediately obvious (or .. at all) .. I'm going to go ahead and assume so, which just leaves me even more confused) 08:33 < waxwing> to be clear 'other address of yours' - i was assuming (perhaps wrongly) that it was an *output* address. 08:33 < cbeams> Right, it's only this one utxo, 3003 as per above that's been involved with this problem. 10:02 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket 10:03 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 10:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket 10:53 -!- Davterrra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 10:53 -!- Davterrra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket 11:08 -!- Davterrra [~davterra@gateway/tor-sasl/tralfaz] has quit [Quit: Leaving] 11:26 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket 11:26 -!- davterra is now known as tralfaz 12:19 -!- rdymac [uid31665@gateway/web/irccloud.com/x-odsewlaeecrhdtzl] has quit [Quit: Connection closed for inactivity] 13:09 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 13:10 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket 13:46 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 13:59 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #joinmarket 14:48 -!- nixbitcoin_ [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has joined #joinmarket 14:48 -!- nixbitcoin [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has quit [Ping timeout: 240 seconds] 15:03 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 16:10 -!- rdymac [uid31665@gateway/web/irccloud.com/x-pamiborgtevlargz] has joined #joinmarket 16:10 -!- tralfaz [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection] 17:07 -!- HackRelay [~jmrelayha@p5de4a114.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 17:07 -!- DSRelBot [~DSRelBot@p5de4a114.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 17:11 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket 17:16 -!- DSRelBot [~DSRelBot@p54866fb6.dip0.t-ipconnect.de] has joined #joinmarket 17:22 -!- HackRelay [~jmrelayha@p54866fb6.dip0.t-ipconnect.de] has joined #joinmarket 17:27 -!- Tom61Sporer [~Tom61Spor@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 240 seconds] 21:47 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 21:47 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket 22:20 -!- rdymac [uid31665@gateway/web/irccloud.com/x-pamiborgtevlargz] has quit [Quit: Connection closed for inactivity] --- Log closed Mon Sep 07 00:00:16 2020