--- Log opened Wed Oct 14 00:00:47 2020
00:37 -!- jonatack [~jon@213.152.161.69] has quit [Ping timeout: 272 seconds]
00:41 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
00:46 < ongo> disablewallet=1 can be set for joinmarket right?
00:46 < belcher> nope
00:46 < belcher> joinmarket needs core's wallet
00:49 -!- Troy14Johns [~Troy14Joh@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 240 seconds]
01:12 -!- Livestradamus [~quassel@unaffiliated/livestradamus] has quit [Quit: I'm out.]
01:12 -!- Livestradamus [~quassel@unaffiliated/livestradamus] has joined #joinmarket
01:18 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection]
01:18 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 260 seconds]
01:18 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #joinmarket
01:18 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #joinmarket
01:20 -!- jonatack [~jon@37.170.11.107] has joined #joinmarket
01:27 -!- jonatack [~jon@37.170.11.107] has quit [Ping timeout: 272 seconds]
01:28 -!- jonatack [~jon@213.152.162.94] has joined #joinmarket
01:39 -!- asy [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
03:24 -!- jonatack [~jon@213.152.162.94] has quit [Ping timeout: 258 seconds]
04:01 -!- waxwing__ [~waxwing@81-178-153-121.dsl.pipex.com] has joined #joinmarket
04:03 -!- waxwing_ [~waxwing@92.40.182.22.threembb.co.uk] has quit [Ping timeout: 256 seconds]
04:11 -!- fiatjaf [~fiatjaf@2804:7f2:2a85:2fc:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 244 seconds]
04:24 -!- fiatjaf [~fiatjaf@2804:7f2:2985:c0dd:ea40:f2ff:fe85:d2dc] has joined #joinmarket
04:41 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds]
04:41 -!- deafboy [quasselcor@cicolina.org] has quit [Remote host closed the connection]
04:42 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #joinmarket
04:42 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
05:04 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket
06:06 -!- fiatjaf [~fiatjaf@2804:7f2:2985:c0dd:ea40:f2ff:fe85:d2dc] has quit [Read error: Connection reset by peer]
06:39 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket
07:24 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection]
07:33 < HackRelay> [hackint-irc/user_Pulp2] Hey guys, can someone give me a quick overview of the differences between `tx_broadcast` option random-peer and not-self?
07:33 < HackRelay> [hackint-irc/user_Pulp2] I'm looking at commit 4440ffb and it says that with not-self if the other parties fail/refuse to broadcast we will end up broadcasting ourself.
07:33 < HackRelay> [hackint-irc/user_Pulp2] What's the difference then with random-peer? Is it that with the latter we don't wait for the timeout?
07:34 < HackRelay> [hackint-irc/user_Pulp2] A related thing, in joinmarket.cfg file, not-self says "never broadcast with your own ip" and then the note says, paraphrasing, that it's not really never but only if a maker does it for you.
07:34 < HackRelay> [hackint-irc/user_Pulp2] I don't understand what the word "never" means here.
07:34 < HackRelay> [hackint-irc/user_Pulp2] Thanks
07:37 < waxwing__> it's an entirely valid question which picks up a potential flaw in what we have now.
07:37 < waxwing__> the problem is almost no makers will actually broadcast.
07:37 < waxwing__> but i think we should patch not-self to be "under no circumstances ourself" as the comment says.
07:38 < waxwing__> so that's my bad really.
07:38 < waxwing__> currently with either option, it will only try to do what the comment says, but then will fall back after iirc 90s and broadcast locally. Or 60s.
07:38 < waxwing__> (i.e. if it doesn't see the broadcast happen of course)
07:43 < HackRelay> [hackint-irc/user_Pulp2] okay, so we can say that as of current master, there's basically no difference between the two? Both try to ask makers to broadcast and fallback to us?
07:49 < waxwing__> no, there is a difference; one selects (all at random), other selects (all except you at random)
07:50 < HackRelay> [hackint-irc/user_Pulp2] nice, thanks for the clarification
07:50 < waxwing__> qubenix, pushed that fix we discussed
07:51 < waxwing__> Pulp2 i'll take a look at that now. specifically making notself never self-broadcast.
07:52 -!- waxwing__ is now known as waxwing
07:52 -!- waxwing [~waxwing@81-178-153-121.dsl.pipex.com] has quit [Changing host]
07:52 -!- waxwing [~waxwing@unaffiliated/waxwing] has joined #joinmarket
07:58 < HackRelay> [hackint-irc/user_Pulp2] sweet, although maybe would be simpler for you to just rephrase it so that it's clear what the difference is.
07:58 < HackRelay> [hackint-irc/user_Pulp2] Maybe is enough that with not-self you broadcast yourself only as last resort while with random-peer is just "random".
07:58 < HackRelay> [hackint-irc/user_Pulp2] I guess the risk would be that people could end up selecting not-self and then be confused when they don't see their transactions broadcast.
07:58 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
07:59 < HackRelay> [hackint-irc/user_Pulp2] Maybe the note should change to make clear that with this option you may be "stuck".
07:59 < HackRelay> [hackint-irc/user_Pulp2] Anyway, just saying, you know better than me.
08:02 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
08:04 < waxwing> yes it's a problem. i was particularly not wanting to think through the implicatoins for schedules of joins like tumbler, it doesn't really gel with that.
08:05 < waxwing> but we have to consider what the purpose of such an option is; a user choosing it presumably has their security model as "i don't want to broadcast directly from this node", otherwise it seems a bit pointless to have the option.
08:05 < waxwing> so ... i'm not 100% sure of the right set of actions to take, but simplest is probably just to disable fallback for that option, and leave the text as-is.
08:06 < waxwing> the kind of power user that would actually choose it, would have to figure out for themselves what to do. they can take the tx hex from the INFO logging output and deal with it themselves.
08:06 < HackRelay> [hackint-irc/user_Pulp2] yeah this makes total sense too
08:28 < HackRelay> [hackint-irc/user_Pulp2] Wondering if then the random-peer option should become the current not-self, so basically:
08:28 < HackRelay> [hackint-irc/user_Pulp2] self = broadcast myself
08:28 < HackRelay> [hackint-irc/user_Pulp2] random-peer = broadcast myself only if no peer does it
08:28 < HackRelay> [hackint-irc/user_Pulp2] not-self = never broadcast myself
09:01 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket
09:01 -!- Anon1515 [b06992d7@176.105.146.215] has joined #joinmarket
09:05 < waxwing> i mean maybe. i think what we have now is marginally more logical, but not sure.
09:05 < Anon1515> Win7 0.7.0 GUI version: I keep getting a "WalletService failed to start due to inability to query block height" error. Would appreciate some help.
09:05 < waxwing> see https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/704 user_Pulp2
09:06 < waxwing> Anon1515, can you make an RPC to bitcoin core outside Joinmarket?
09:06 < waxwing> RPC *call
09:06 < Anon1515> I actually got past it once, and then it got stuck checking the wallet
09:07 < Anon1515> What's the easiest way to test that?
09:07 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
09:08 < waxwing> using bitcoin-cli in a terminal, i think
09:09 < waxwing> btw there is 0.7.1 GUI now
09:09 < waxwing> there was actually one fix related to that issue, i'm not sure if it'll change your situation, but download the new one and check the gpg signature.
09:14 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket
09:22 < Anon1515> waxwing Getting the latest version fixed the problem, so now I'm back to where I was yesterday. It gets stuck on 'Reading wallet from blockchain'. I assume that's not supposed to be a full rescan for an empty wallet, but I left it running for a couple of hours last time, and it didn't finish. I'll post the in-program log.
09:22 < Anon1515> DEBUG:Looking for wallet in: ('C:/Users/XXXXXXX/AppData/Roaming/joinmarket/wallets/wallet.jmdat', 'All Files (*)')
09:24 < Anon1515> Okay, the Reading... just disappeared, but the JM wallet tab still says "No wallet loaded.".
09:28 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds]
09:30 -!- jonatack [~jon@109.202.107.147] has joined #joinmarket
09:33 < Anon1515> The ".wallet.jmdat.lock" is present, though.
10:11 -!- openoms [~quassel@91.132.136.76] has quit [Ping timeout: 260 seconds]
10:11 < waxwing> sounds like there's a problem with the rpc calls .. somehow .. in coinjoins tab do you see any log messages at the bottom?
10:11 -!- openoms [~quassel@91.132.136.76] has joined #joinmarket
10:15 < Anon1515> waxwing Yeah, posted it above.
10:21 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has quit [Remote host closed the connection]
10:22 -!- davterra [~davterra@gateway/tor-sasl/tralfaz] has joined #joinmarket
10:24 < Anon1515> (The XXXXXXX part is stuff I redacted, of course. Just being paranoid.)
10:25 < waxwing> that's not an rpc error though (actually it's not an error message at all)
10:26 < waxwing> i think you might need to give more information about what you're doing. how is your Bitcoin Core set up (different or same machine), how did you set the blockchain settings in the config file
10:27 < waxwing> and when you started Qt did you get the initial error message telling you to setup the config file?
10:27 < waxwing> i'm guessing not for the latter, since you already ran this before (an older version)
10:27 < waxwing> and presumably you've only done wallet->load wallet in the menu and nothing else.
10:27 < waxwing> and were you ever able to load the wallet in the earlier version.
10:29 < Anon1515> "how is your Bitcoin Core set up (different or same machine)"
10:29 < Anon1515> same machine
10:30 -!- EvanitoC [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
10:30 < Anon1515> "and when you started Qt did you get the initial error message telling you to setup the config file?" Yes, with the last version.
10:30 < Anon1515> Not after updating.
10:30 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Ping timeout: 240 seconds]
10:31 < Anon1515> "and presumably you've only done wallet->load wallet in the menu and nothing else.
10:31 < Anon1515> "and were you ever able to load the wallet in the earlier version.
10:33 < Anon1515> "how did you set the blockchain settings in the config file" JM's config file? bitcoin-rpc, no, localhost, 8332, [same user as BC config], [same pass as BC config], blank
10:34 < waxwing> did you generate that wallet.jmdat in Qt?
10:34 < Anon1515> The GUI? Yes.
10:34 < Anon1515> In version 0.7.0
10:35 < waxwing> and did you generate it using the same Bitcoin Core instance?
10:36 < Anon1515> Yes. I did a bit of settings-tweaking and restarting (both BC and JM) trying to get past the block height error, but I haven't changed computers or updated Bitcoin Core or anything like that.
10:37 < waxwing> so did you manage to load the wallet before? if it generated OK it'd be a bit strange if it didn't load.
10:38 < Anon1515> No. I've had some other issues (most of them self-inflicted), but trying to load the wallet is as far as I've gotten.
10:38 < waxwing> i see, so even when you were on 0.7.0 "Load Wallet" didn't succeed, it just hung?
10:39 < waxwing> again take a look at the bottom section of the Coinjoins tab, there is a logging output area there, there might be some other messages.
10:40 < Anon1515> It always kept going for a while (Loading Wallet, or somesuch), and then the loading text disappeared.
10:40 < Anon1515> I posed the CJ tab log above, I'll copypaste.
10:40 < Anon1515> DEBUG:Looking for wallet in: ('C:/Users/XXXXXXX/AppData/Roaming/joinmarket/wallets/wallet.jmdat', 'All Files (*)')
10:40 < waxwing> ah, i see. nothing else.
10:40 < waxwing> hmm.
10:41 < Anon1515> Just noticed that after trying to load the wallet, the Wallet -> Show Seed option accurately reports the recovery seed.
10:41 < waxwing> i'd suggest checking firewall settings, except i think it should fail earlier than that if that were the problem.
10:41 < waxwing> oh. so .. the wallet is loaded, i guess.
10:41 < waxwing> so you see nothing at all in the wallet tab (i.e. no addresses)?
10:41 < waxwing> the wallet tab is the first, default tab.
10:41 < Anon1515> "No wallet loaded. Use blah blah"
10:42 < waxwing> ok that's really weird.
10:42 < Anon1515> Same text as before you try to load anything.
10:42 < waxwing> anyone else got an idea? kristapsk_ ?
10:43 < waxwing> Anon1515, oh one thing, please change `console_log_level` to DEBUG in `joinmarket.cfg` then try again, and note again the logging output.
10:47 < Anon1515> waxwing Changed it and restarted. Same output as what I posed above.
10:47 < waxwing> ok. worth a try i guess.
10:48 < Anon1515> Tried disabling firewall and AV, no luck.
10:48 < waxwing> yeah that was very unlikely to be it, but good to check
10:50 < waxwing> your node is synced right?
10:51 < waxwing> also try `bitcoin-cli getblockcount` on a terminal, i think/hope bitcoin-cli shoudl work, you might need to navigate the Bitcoin Core directories
10:51 < Anon1515> 652736, which seems accurate
10:52 < Anon1515> Okay, I'll try
10:52 < waxwing> yeah that' sup to date
10:55 < waxwing> if i had to guess what's happening, it might be that it's crashing because of an underlying bug, but silently.
10:55 < waxwing> it's always possible that there's some incompatibility here on Win7. I didn't test that, only Win10.
10:55 < Anon1515> cli reports same
10:55 < waxwing> i could make a debug version of the build for you, then it would start from the terminal, and if it crashes you'll see the error message there.
10:55 < waxwing> but then again .. Qt doesn't crash. still, it's at least possible.
10:57 < waxwing> hmm and if showseed works then the bitcoin libraries are clearly working fine. damn this is a hard one.
10:57 < Anon1515> Maybe I should try the command line version of JM first. Was hoping I was missing something obvious and easy to fix, but that doesn't seem to be the case.
10:57 < waxwing> i mean i don't know how easy it'd be to run command line on win7. all our instructions are for win10.
10:57 < waxwing> it might not be possible, not sure.
10:58 < waxwing> instructions are in docs/INSTALL.md
11:03 < Anon1515> Does it require Python 3.9.0?
11:03 < waxwing> py3.6+ 
11:03 < Anon1515> Because that's when they stopped W7 support
11:04 < Anon1515> okay
11:09 < Anon1515> Might as well try the debug version. Would be nice to get the GUI working.
11:09 < waxwing> ok i'll build it. but if it's a win7 thing there might not be a solution, let's see.
11:23 -!- waxwing_ [~waxwing@92.40.183.116.threembb.co.uk] has joined #joinmarket
11:24 < waxwing_> Anon1515, see https://github.com/JoinMarket-Org/joinmarket-clientserver/releases/tag/v0.7.1 i added a win7-debug exe at the bottom
11:24 < waxwing_> it should open a console whne you double click it and you might find that you see errors there
11:26 -!- waxwing [~waxwing@unaffiliated/waxwing] has quit [Ping timeout: 260 seconds]
11:30 < Anon1515> So far, it outputs the same thing as the GUI log I posed above.
11:30 < Anon1515> Only difference is the 'getblockchaininfo' at the top.
11:31 < Anon1515> And the user data location path being listed.
11:32 < Anon1515> 'Loading wallet' just disappeared, and nothing new in the log.
11:32 < Anon1515> 'listlabels' is the last entry in both the console and GUI
11:35 < waxwing_> ok. if there are no crashes either then i'm currently stumped.
11:36 < Anon1515> Okay, thanks anyway. I'll ditch the GUI and give the normal version a try.
11:37 < waxwing_> on win10 i haven't heard of such problems fwiw
12:19 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
12:19 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket
12:19 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket
12:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
12:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
12:22 -!- belcher_ is now known as belcher
12:22 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
13:06 -!- Anon1515 [b06992d7@176.105.146.215] has quit [Remote host closed the connection]
13:10 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
13:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
13:23 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
13:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
13:28 -!- deafboy [quasselcor@cicolina.org] has quit [Quit: deafboy]
13:28 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
13:45 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 264 seconds]
13:55 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
14:02 -!- asy [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
17:05 -!- HackRelay [~jmrelayha@p5de4a521.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
17:05 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket
17:05 -!- DSRelBot [~DSRelBot@p5de4a521.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
17:08 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.9]
17:18 -!- DSRelBot [~DSRelBot@p5de4a634.dip0.t-ipconnect.de] has joined #joinmarket
17:20 -!- HackRelay [~jmrelayha@p5de4a634.dip0.t-ipconnect.de] has joined #joinmarket
18:05 -!- fiatjaf [~fiatjaf@2804:7f2:2a84:12c:ea40:f2ff:fe85:d2dc] has joined #joinmarket
18:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
19:03 -!- Livestradamus [~quassel@unaffiliated/livestradamus] has quit [Ping timeout: 246 seconds]
19:19 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket
19:27 -!- Livestradamus [~quassel@unaffiliated/livestradamus] has joined #joinmarket
20:52 -!- EvanitoC [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
20:55 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
22:56 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
22:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #joinmarket
23:22 -!- waxwing__ [~waxwing@81-178-153-121.dsl.pipex.com] has joined #joinmarket
23:25 -!- waxwing_ [~waxwing@92.40.183.116.threembb.co.uk] has quit [Ping timeout: 256 seconds]
23:35 -!- dave_uy [~david@108.61.193.26] has quit [Quit: The Lounge - https://thelounge.chat]
23:38 -!- dave_uy [~david@108.61.193.26] has joined #joinmarket
--- Log closed Thu Oct 15 00:00:47 2020