--- Day changed Fri Nov 01 2019
01:27 < belcher> im currently writing another blockchain interface that uses scantxoutset to sync without needing to rescan (but with other tradeoffs), iv found there are quite a few places where the blockchain interface abstraction isnt used, the code assumes the only kind of bci is BitcoinCoreInterface
01:29 < belcher> im fixing or working around those places slowly where they come up
01:29 < belcher> kristapsk i thought of that method but its still vulnerable to sybil attacks, theres no guarantees that the different electrum servers arent actually owned by the same entity
01:30 < belcher> it might be worth doing anyway though, idk it depends on the user's threat model really
01:30 < belcher> client side block filtering seems to be the best way though, even if it does use much more data
01:31 < waxwing> yes i already realised in more than one sense that wallet_service is not relying enough on bci to give it stuff, it's not fully encapsulated. but at the very least we should try to keep all bci access there and clients only talk to wallet service.
01:32 < waxwing> then fixing up the bci module itself can be done in isolation (including moving methods from child to parent, or adding new bcis.
01:36 < belcher> yep agreed
02:54 < waxwing> from a quick search, outside regtest and test cases (of which there are a lot), the only "direct" access to bc_interface i see is calling pushtx in Taker. we could change that but it's maybe nbd.
02:56 < belcher> direct access to bc_interface is fine isnt it, the less ideal parts are access to bc_interface.rpc() which assumes BitcoinCoreInterface
03:44 < waxwing> yes. but even the former is better removed, just i guess it isn't much of a priority.
03:48 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 260 seconds]     
03:51 < belcher> agreed its not a priority, everything works fine and BitcoinCore is the only interface worth knowing about.. i only noticed this abstraction stuff when writing BitcoinCoreNoHistoryInterface
03:51 < belcher> i guess in the future when someone write ClientSideBlockFilteringInterface they can fix the abstractions as needed
07:07 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has quit [Remote host closed the connection]     
07:07 -!- technonerd [~techno@gateway/tor-sasl/technonerd] has joined #joinmarket     
08:13 -!- MaxSan [~four@195.206.105.203] has joined #joinmarket     
08:20 -!- k1tsun3 [~k1tsun3@unaffiliated/k1tsun3] has joined #joinmarket     
08:22 < k1tsun3> Can i run the bitcoin core rpc from the gui or do i need to do it via command line?
08:27 < belcher> the bitcoin core RPC isnt something thats run on its own
08:28 < belcher> what are you trying to do? i think your question is a little confused
08:28 < belcher> rpc means remote procedure call, its a protocol
08:29 < k1tsun3> What i mean is, it that a feature specifically of the CLI interface
08:31 < k1tsun3> or if i set the correct options in bitcoin.conf and run the core wallet gui, will it still start the RPC server the same way?
08:33 < belcher> yes it will start the rpc server in the same way
08:33 < belcher> regardless of whether you run bitcoind or bitcoin-qt
08:33 < belcher> you can always check by running `netstat -l` and see if the RPC port (usually 8332) is open
08:35 < k1tsun3> alright thanks
08:36 < k1tsun3> also, im running joinmarket and btcore on whonix, is there anything i have to change besides the IRC servers for use with tor?
08:43 -!- midnightmagic is now known as midnight     
08:43 < belcher> nope, just change to the tor onions and enable socks5 proxy
08:43 < belcher> its all in joinmarket.cfg
08:43 -!- midnight is now known as midnightmagic     
08:43 -!- midnightmagic is now known as midnight     
08:49 < k1tsun3> I need to enable the socks5 proxy if im already running whonix?
09:03 < belcher> tor works by opening a socks5 proxy port
09:03 < belcher> on port 9050 or possibly port 9150
09:11 -!- simon_ [~simon@93-238-145-85.ftth.glasoperator.nl] has joined #joinmarket     
09:16 < simon_> is there a way to check how many joinmarket transactions are executed on a daily/weekly basis?
09:17 < belcher> in theory there could be a script which scans the blockchain and counts them
09:18 < belcher> there is this code https://www.reddit.com/r/joinmarket/comments/c7wvoe/stats_collected_from_the_blockchain_over_a_few/
09:18 < belcher> that code may have false positives though
09:20 < simon_> thanks, i'll have a look at it
09:21 < belcher> if you're aiming to improve that code, theres a paper on joinmarket which has some good heuristics that gets the false positives down to basically zero
10:19 < k1tsun3> belcher: i get that, but whonix routes all traffic on a VM through the tor network. Would that not be tor over tor if i enabled the socks5 proxy?
10:19 < belcher> ah ok, i didnt know
10:19 < belcher> im not sure, id say you should try both ways with and without telling joinmarket to use a socks5 proxy server
10:20 < k1tsun3> alright thankyou
11:57 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket     
12:01 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]     
12:01 -!- reallll is now known as belcher     
12:02 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket     
13:06 < kristapsk> I am the only one who have noticed that recently the number of "Makers who didnt respond" has increased?
13:24 < simon_> thanks again @belcher, it isn't my first intention to improve the code but that might come useful :)
13:34 < qubenix> k1tsun3: it's not tor over tor. provide your gateway ip as the socks5_host, and use a different port for each server to get stream isolation.
13:36 < qubenix> k1tsun3: what is the host os on your system?
13:37 < k1tsun3> ubuntu
13:38 < k1tsun3> qubenix: im running the whonix workstation through the whonix gateway on ubuntu
13:38 < qubenix> ok, i asked because i have a nice guide for qubes.
13:43 < k1tsun3> do you have any experience with whonix?
13:44 < k1tsun3> because im dont know how to configure it to use a different port for stream isolation
13:52 < qubenix> you do `cat /usr/share/tor/tor-service-defaults-torrc` in the gateway to see the ips whonix has allocated for tor. i use 9180-9182 for mine, but there's plenty to choose from. you might also notice that whonix has 9111 dedicated for bitcoind, you should set that as well (with the gateway ip) in your bitcoin.conf as proxy= *and* onion=. if you don't set onion= then bitcoind will not use the proxy (it 
13:52 < qubenix> will use the default tor proxy) for onion addresses.
13:56 < k1tsun3> so in bincoin.conf i set proxy and onion =[gatewayip]:(torport)
13:57 < qubenix> yep. i mean you don't need to do it, but this gives you stream isolation (better privacy). for bitcoin.conf use port 9111 for both proxy and onion.
13:57 < k1tsun3> or sorry, [gatewayip]:9111 for bitcoin.conf, and [gatewayip]:(9180-9182) for joinmarket.cfg
13:58 < k1tsun3> perfect, thank you a ton you cleared a lot up for me
13:58 < qubenix> in joinmarket.cfg each server gets its own gatway:port
13:59 < k1tsun3> but there wouldnt be more than one server right?
13:59 < k1tsun3> since im running it straight through whonix
14:01 < qubenix> joinmarket connects to multiple irc servers
14:01 < k1tsun3> oh via the irc servers my bad
14:02 < k1tsun3> would the rpc use a different gateway and port since im using tor
14:02 < k1tsun3> in the joinmarket cfg
14:04 < qubenix> no because the bitcoind rpc is running on the same workstation. isn't it?
14:04 < k1tsun3> yes     
14:05 < qubenix> with qubes i have a setup where each application runs in it's own workstation and the comm using qubes qrexec. my joinmarket wallet runs with no networking. :)
14:09 < k1tsun3> i would switch to qubes but i just spent 2 days downloading the entire blockchain onto the whonix workstation through tor and i dont want to do that again
14:09 < qubenix> save it to a drive
14:09 < k1tsun3> and if im not mistaken, the socks5 proxy in joinmarket.cfg gets [gateway][9180-9182]
14:11 < qubenix> here's a sample config: https://termbin.com/ub5i
14:11 < k1tsun3> so besides doing that, setting the irc servers to the onion versions, and setting the proxy & onion to [gateway]:(9111) there shouldnt be any other edits i need to make?
14:11 < qubenix> not everything applies to you, but you can see how the servers are setup
14:12 < qubenix> yes is the answer to your last question
14:12 < k1tsun3> alright perfect, you've been a ton of help man
14:12 < qubenix> np, make some coinjoins
14:22 -!- k1tsun3 [~k1tsun3@unaffiliated/k1tsun3] has quit [Quit: Leaving]     
14:53 -!- simon_ [~simon@93-238-145-85.ftth.glasoperator.nl] has quit [Quit: simon_]     
15:51 -!- King4Labadie [~King4Laba@ns334669.ip-5-196-64.eu] has joined #joinmarket     
16:12 < AgoraRelay> [agora-irc/AlexCato1] About this: k1tsun3] belcher: i get that, but whonix routes all traffic on a VM through the tor network. Would that not be tor over tor if i enabled the socks5 proxy?
16:13 < AgoraRelay> [agora-irc/AlexCato1] yes, it would try to route the joinmarket traffic through TOR, but the IRC servers that joinmarket connects to might not allow TOR connections unless explicitly using the configured TOR ports
16:14 < AgoraRelay> [agora-irc/AlexCato1] so you want to use the (commented out) TOR config for the joinmarket IRC servers in joinmarket.cfg; just to get it to work.
17:34 < qubenix> why is the default confirm_timeout_hours so low? 6 hours for confirmation gets passed fairly often in my experience.
17:38 -!- King4Labadie [~King4Laba@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds]     
17:50 < AgoraRelay> [agora-irc/AlexCato1] it's from back in the time when 6 hours was exceptionally long, way pre-2017 (when I've seen some coinjoins take many weeks). Indeed should be adjusted
18:06 -!- StopAndDecrypt_ [~StopAndDe@107.181.189.37] has joined #joinmarket     
18:07 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection]     
18:30 -!- k1tsun3 [~kitsune@unaffiliated/k1tsun3] has joined #joinmarket     
18:30 < k1tsun3> is the bitcoin config file supposed to be blank by default?
18:42 -!- AgoraRelay [~jmrelayfn@p5DE4A6D6.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]     
18:45 -!- CgRelayBot [~CgRelayBo@p5DE4A6D6.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds]     
18:55 -!- CgRelayBot [~CgRelayBo@p5DE4A35A.dip0.t-ipconnect.de] has joined #joinmarket     
18:57 -!- AgoraRelay [~jmrelayfn@p5DE4A35A.dip0.t-ipconnect.de] has joined #joinmarket     
19:04 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket     
19:10 < qubenix> k1tsun3: yes, at least historically. i'm not even sure it exists by default, i'm pretty sure i always created mine.
19:31 -!- StopAndDecrypt_ [~StopAndDe@107.181.189.37] has quit [Ping timeout: 268 seconds]     
19:32 -!- StopAndDecrypt [~StopAndDe@107.181.189.37] has joined #joinmarket     
19:32 -!- StopAndDecrypt [~StopAndDe@107.181.189.37] has quit [Changing host]     
19:32 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
20:39 < k1tsun3> i keep getting an error on the install.sh with libsodium starting with sha265sum: libsodium-1.0.13.tar.gz, No such file or directory 
20:41 < k1tsun3> should i follow the install.md or the joinmarket-qt-guide.md
20:43 < k1tsun3> if im trying to use joinmarket-qt
20:47 < takinbo> k1tsun3: can you find out if the command `sha256sum` works directly on your shell? it might be that it is not available and needs to be installed.
20:51 < k1tsun3> takinbo: fixed, thankyou
20:51 < takinbo> yw     
20:52 < k1tsun3> wait nevermind
20:52 < k1tsun3> i spoke too soon
20:52 < k1tsun3> sha265sum was not installed, i installed it and same error
20:58 < k1tsun3> actually i cant even install sha265sum... im on ubuntu and its saying sha265sum command cannot be found and the package also cannot be found
20:58 < takinbo> try installing the coreutils package. 
21:03 -!- k1tsun3 [~kitsune@unaffiliated/k1tsun3] has quit [Ping timeout: 245 seconds]     
21:10 -!- k1tsun3 [~kitsune@unaffiliated/k1tsun3] has joined #joinmarket     
21:10 < k1tsun3> if i install using the install.md instructions will it still install joinmarket-qt?
21:12 < takinbo> yes. running install.sh will present a prompt to install joinmarket-qt
21:15 < k1tsun3> no install.sh isnt working
21:15 < k1tsun3> takinbo: install.sh keeps erroring out on sha256sum for libsodiumdev
21:17 < takinbo> did you install the coreutils ubuntu package? `apt install coreutils`
21:18 < k1tsun3> already installed
21:19 < k1tsun3> like it was installed beforehand
21:19 < takinbo> it should have
21:19 < takinbo> the only other alternative is that libsodium is not being downloaded
21:21 < takinbo> can you check if the file was downloaded to `deps/cache`?
21:22 < k1tsun3> am i looking for the libsodium-1.0.13.tar.gz? 
21:22 < k1tsun3> that is not there
21:22 < takinbo> other files?
21:24 < k1tsun3> i have a long string of numbers and letters.tar.gz, 9.0.0.tar.gz, and v3.2.1.tar.gz 
21:25 < k1tsun3> takinbo: i also get the error unlink: cannot unlink './libsecp256k1': no such file or directory. Could this have something to do with the issue?
21:25 < takinbo> ok, that means other packages are being downloaded. can you try running install.sh again?
21:26 < k1tsun3> ive ran it about 5 times same issue each time
21:26 < takinbo> no that would probably be a different problem
21:26 < takinbo> okay, delete the deps folder and try it again. 
21:26 < k1tsun3> i've also tried deleted and re-downloading the files from github
21:26 < k1tsun3> but okay
21:27 < k1tsun3> should i run it as sudo or no?
21:28 < takinbo> no. you don't need sudo.
21:30 < k1tsun3> alright so i can see that the libsodium file is not being downloaded
21:31 < k1tsun3> its saying that i cant use curl because my ssl certificates are not valid?
21:33 < k1tsun3> i think i narrowed the error down, its saying that curl failed to verify the legitimacy of the server
21:33 < k1tsun3> could that be the issue?
21:35 < takinbo> yes. ensure you have `ca-certificates` installed
21:35 < takinbo> and try running the script again. 
21:36 < k1tsun3> ca-certificates already installed
21:36 < k1tsun3> and its only failing to download libsodium for whatever reason
21:37 < k1tsun3> could it be the libsodium server certificates that are invalid for some reason?
21:38 < takinbo> they are valid and issued by letsencrypt and i think you don't have the root certs in your certs store for letsencrypt that's why it's failing
21:39 < k1tsun3> where do i get those?
21:39 < takinbo> can you try updating? `sudo apt update && sudo apt upgrade`
21:42 < k1tsun3> after the upgrade should i try to run it again?
21:43 < takinbo> yes     
21:48 -!- k1tsun3 [~kitsune@unaffiliated/k1tsun3] has quit [Ping timeout: 250 seconds]     
21:55 -!- k1tsun3 [~kitsune@unaffiliated/k1tsun3] has joined #joinmarket     
22:14 < k1tsun3> alright i upgraded, same issue
22:15 < k1tsun3> i wonder why all the other files are able to download but libsodium wont?
22:25 < takinbo> the only explanation i could come up with is letsencrypt
22:25 < k1tsun3> how do i get the correct certs?
22:26 < takinbo> k1tsun3: you might have some success using a method similar to this: https://blog.rac.me.uk/2016/05/04/techy-getting-curl-to-work-with-lets-encrypt-unable-to-get-local-issuer-certificate-error/