--- Log opened Fri Jan 03 00:00:57 2020
00:35 < AgoraRelay> [agora-irc/AlexCato1] if a coinjoin fails in the process (while makers and takers negotiate all the details) and needs to be restarted, it will be done with new temporary addresses (e.g. for change output). These addresses that end up not being used in the failed process will never be seen/appear on the blockchain
00:36 < AgoraRelay> [agora-irc/AlexCato1] if that happens A LOT (from experience of the last months: it doesn't happen much, just occassionally - so all defaults usually work just fine), in wallet recovery this gap limit might need to be adjusted so that all coins can be found in the recovery process
03:06 -!- Jameson12Moscisk [~Jameson12@ns334669.ip-5-196-64.eu] has joined #joinmarket
03:13 -!- Jameson12Moscisk [~Jameson12@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 258 seconds]
03:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 258 seconds]
03:50 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
04:00 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Quit: Leaving]
04:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
04:01 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
05:11 < adlai> whenever the argument of whether "the onion router"'s name is an acronym comes up, the most prominent image in my mind is that of a certain chapter from _The Hound of the Baskervilles_
05:13 < adlai> zndtoshi: you can also use the skipped addresses for studying the history of market activity, when you recover old wallets
05:13 < adlai> i.e., at what times were clients denying service, paying for deanonymization, etc
05:15 < adlai> might wanna s/ssl/tls/ in the /topic for extra correctness :)
06:39 < waxwing> i'm strongly inclining towards merging 391 now, although we need more tests ideally they don't seem to be forthcoming. i don't think there's still arguments against it are there?
06:39 < waxwing> on 475 i think it's ready, i've done a bit of tests. so that could come after.
06:41 < waxwing> wrt 462 cindiv hasn't answered my point on it, and since it's not really a needed thing right now (could well be useful for performance), and isn't actually properly coded yet, i think probably best just put it on hold.
06:43 -!- trotski2000_ [uid206086@gateway/web/irccloud.com/x-kyxjgtijkbldajzj] has joined #joinmarket
06:43 < waxwing> 395 slipped through the cracks, i mostly just remember being slightly confused about it. kristapsk do you happen to remember the current thinking/status?
07:02 < dave_uy> Is it important to set an IRC password for JoinMarket when using yield-generator-basic.py ?
07:02 < waxwing> dave_uy, no you shouldn't need it
07:02 < waxwing> are you using the tor host settings?
07:04 < dave_uy> I think so. I am connecting through Tor. Trying out with testnet currently.
07:05 < waxwing> ok, but there isn't really a testnet pit running .. depending on exactly what you're trying it might not work.
07:05 < waxwing> you could just try mainnet with a tiny amount of money just to see if everything connects properly.
07:06 < waxwing> personally for development work i completely gave up on testnet(3) because it's so unreliable, use regtest and mainnet only nowadays.
07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
07:07 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has joined #joinmarket
07:07 < dave_uy> OK. I can see that my setup is trying to create a testnet offer. It is OK if it doesn't work.
07:09 < waxwing> one detail that may help whatever you're trying to assess: when you use testnet in the config, the joinmarket channel name has "-test" appended, so it'll be usually "joinmarket-pit-test"
07:09 < waxwing> err #joinmarket-pit-test i mean
07:14 < waxwing> takinbo, you ok with me merging 391 now?
07:15 < dave_uy> joined:  #joinmarket-pit-test cgan.onion.garlic
07:15 < dave_uy> I had that in my daemon [DEBUG]
07:15 < waxwing> did you get to "Jmdaemon setup complete" ?
07:16 < waxwing> that's the last log message indicating you've reached ready status
07:16 < dave_uy> Yes
07:17 < dave_uy> Does yield-generator-basic.py use all funds in wallet?
07:17 < waxwing> well then it's "working" but ofc you can only be sure if you set up another wallet+bot to take Taker side and start a join.
07:17 < waxwing> because no one else is there
07:17 < waxwing> it only co-spends coins from within the same mixdepth(=account). have you read about how it works in USAGE.md ?
07:18 < dave_uy> Right. I'll test some mainnet BTC once I get my setup working how I want.
07:18 < waxwing> hmm well, actually the USAGE file mostly explains more basic things, including how the wallet is organized, the file https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/YIELDGENERATOR.md only gives very basic details.
07:18 < dave_uy> I'm reading about it now. I'll keep going with the USUAGE.md
07:18 < waxwing> be sure to read the lines at the top of the yield generator script also, for the parameters.
07:26 < dave_uy> So, mixdepth is equivalent to "account" as many other wallets call it? And yield generator will try to mix from all mixdepths based on the --mixdepth ?
07:27 < dave_uy> I guess the default for --mixdepth is 5.
07:47 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 268 seconds]
07:54 < waxwing> dave_uy, yes technically the mixdepths are bip32 accounts. but the best way to think of them is as separate wallets.
07:54 < waxwing> so the idea is that when your bot source coins as inputs to a coinjoin it only takes coins from one mixdepth.
07:55 < waxwing> and the transfer from mixdepth to mixdepth is only via equal sized coinjoin outputs.
07:55 < waxwing> while the change outputs go back to the same mixdepth(wallet)
08:00 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket
08:07 < dave_uy> Does mixdepth to mixdepth transfers happen automatically with the coinjoins?
08:19 < waxwing> yes. i've just spent a fair few minutes looking through our docs and irritatingly i can't find anything that addresses this basic point, at least not directly.
08:20 < waxwing> as i said above, equal sized coinjoin outputs are where the transfer from mixdepth to mixdepth occurs. think of that as transferring between different wallets of yours, as i said.
08:20 < waxwing> if we didn't do that then the coinjoin outputs will often be trivially linkable to the original wallet, thus destroying the purpose of doing the coinjoin - you could figure out who owned which equal sized output.
08:21 < waxwing> you may find reviewing these transaction type diagrams instructive: https://github.com/JoinMarket-Org/JoinMarket-Docs/blob/master/High-level-design.md#joinmarket-transaction-types
08:22 < waxwing> (though much of what's in that repo (Joinmarket-Docs) is out of date, but those diagrams are correct.
08:22 < waxwing> dave_uy, ^
08:31 -!- avril [wha@unaffiliated/avril] has quit [Ping timeout: 260 seconds]
08:36 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket
08:49 < kristapsk> waxwing, about 391, didn't found a time to test properly, mainly due to all this Christmas / New Year stuff; will try to look at it now
08:50 < kristapsk> waxwing, about 395 - I think there just wasn't clear consensus in merging that (I'm using it on my laptop when testing stuff sometimes, where that's the only way to select default Core wallet)
09:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
09:10 < waxwing> kristapsk, in addition to your point about 0.18 (good catch) i think it's also the case that the test failed on MacOS. I think the latter is likely just a timing issue though.
09:57 -!- zndtoshi [4f700049@79.112.0.73] has quit [Remote host closed the connection]
11:10 < openoms> Would there be an easy way to make JM torify the RPC connection?
11:11 < openoms> The usecase would be to use joinmarket-QT with a remote full-node.
11:12 < openoms> Have already made it work on LAN, but a Tor  connection would even make that easier routing around the firewalls and provide a secure tunnel.
11:17 -!- trotski2000_ [uid206086@gateway/web/irccloud.com/x-kyxjgtijkbldajzj] has quit [Quit: Connection closed for inactivity]
11:18 < kristapsk> openoms, I think "torify python joinmarket-qt.py" could be the way, by looking fast at code it looks like a problem could be that python's http.client would not support .onion hosts, so some handling would be needed in jmclient/jmclient/jsonrpc.py
11:23 < openoms> thanks kristapsk will try and report
11:33 < dave_uy> waxwing: Thank you for sending the chart. Should I spread out the BTC in different mix depths? Or will JoinMarket move from mixdepth 0 to 1 through 4 when coinjoining?
11:48 < adlai> openoms: what deanonymization vectors concern you? `torify'-ing the RPC connection will do quite little about most, and arguably opens up at least one additional vector, while merely thickening the motor oil of the router
12:13 < openoms> adlai: to be clear I am aiming to connect to a full node  of mine remotely via Tor. 
12:15 < openoms> a desktop laptop/PC does not have any problem with the added computational requirement of  Tor. Also my RPi4 should take it as it is running multiple Hidden Services without any issue.
12:36 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has joined #joinmarket
12:43 < openoms> kristapsk: the `python joinmarket.py works`
12:45 < openoms> created a Hidden Service for 8332 on the node, copied to the joinmarket.cfg and started successfully
12:46 < openoms> this could work om Tails too.. (could be an iteration of  TailsJoin)
12:51 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 240 seconds]
13:32 < waxwing> openoms, you said "the `python joinmarket.py works`" .. did you mean "the `torify python joinmarket.py` works" .. or?
13:53 < openoms> waxwing: yes, sorry, bloody mobile.
13:53 < openoms> Running
13:53 < openoms> torify python joinmarket-qt.py
13:56 < openoms> it only gives one warning: 1578088278 WARNING torsocks[9010]: [syscall] Unsupported syscall number 217. Denying the call (in tsocks_syscall() at syscall.c:488)
13:59 < openoms> but syncs the wallet successfully
13:59 < kristapsk> openoms, looks like a https://trac.torproject.org/projects/tor/ticket/28861, maybe you should upgrade torify?
14:12 < openoms> my tor is the latest 0.4.2.5-1~bionic+1
14:12 < openoms> torify -v shows torsocks 2.2.0
14:18 < k3tan> openoms, what's the joinmarket.cfg change to use a node on the LAN? 
14:23 < openoms> @k3tan you just need to put your LAN address to rpc_host =
14:25 < openoms> also need to edit the bitcoin.conf on the full node: https://github.com/rootzoll/raspiblitz/issues/842#issuecomment-570615900
14:25 < openoms> and open ufw is used
14:27 < openoms> will add thsi to my joinmarket guide soon
14:53 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has quit [Remote host closed the connection]
15:12 < waxwing> dave_uy, i think it says in the intro that you can just fund in mixdepth 0 and that's fine. as for where it goes, it moves through the mixdepths, initially filling them out and then over time spreading them fairly randomly.
15:12 < waxwing> just one funding tx is fine
15:51 < k3tan> openoms, thanks!
16:12 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 265 seconds]
16:19 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
17:05 -!- AgoraRelay [~jmrelayfn@p5DE4ACBC.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
17:05 -!- CgRelayBot [~CgRelayBo@p5DE4ACBC.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
17:05 -!- slivera [slivera@gateway/vpn/privateinternetaccess/slivera] has joined #joinmarket
17:18 -!- CgRelayBot [~CgRelayBo@p5DE4A299.dip0.t-ipconnect.de] has joined #joinmarket
17:21 -!- AgoraRelay [~jmrelayfn@p5DE4A299.dip0.t-ipconnect.de] has joined #joinmarket
17:39 < felix34> if I want to donate a % of all my joinmarket transactions to support JM development, is there a config file option for that?
17:43 < felix34> (and if not, there should be!)
18:01 -!- AgoraRelay [~jmrelayfn@p5DE4A299.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
18:02 -!- CgRelayBot [~CgRelayBo@p5DE4A299.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds]
18:13 -!- AgoraRelay [~jmrelayfn@p5DE4A1F1.dip0.t-ipconnect.de] has joined #joinmarket
18:14 -!- CgRelayBot [~CgRelayBo@p5DE4A1F1.dip0.t-ipconnect.de] has joined #joinmarket
20:05 -!- avril [wha@unaffiliated/avril] has joined #joinmarket
21:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 240 seconds]
21:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket
21:25 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
21:25 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
22:13 < CgRelayBot> [cgan/kn07] ping
22:49 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
23:30 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket
--- Log closed Sat Jan 04 00:00:56 2020