--- Log opened Mon May 04 00:00:11 2020 01:55 -!- Kelli44Koch [~Kelli44Ko@static.57.1.216.95.clients.your-server.de] has joined #joinmarket 02:11 < waxwing> (to other devs) So a couple of things: first, please take a look at this summary: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/536#issuecomment-623349586 02:12 < waxwing> that's because i know there's a ton of stuff in that thread, so i wanted to make it easy to see where we are 02:12 < waxwing> second, before that gets merged (see first bullet point), it's clear we need a new release for what we have now (so that'd be 0.6.3), and that would be the last release supporting pre-3.6 python as per earlier discussions. 02:13 < waxwing> so i think it's important to decide which existing PRs should be added before tagging that release. 02:13 < waxwing> i think i'll just add TLS support as per the above thread, so that the bip79++ payjoin is in fully testable state (i.e. you could throw it at a btcpayserver), then i'll review the fidelity bond wallet. 02:14 < waxwing> then maybe review one or two more PRs and then go for making that 0.6.3. 02:14 < waxwing> thoughts? 02:42 < Evanito> :o 02:42 < adlai> are fidelity bonds that far along? 02:42 < adlai> seems as though i'm the only person to have voiced opposition to that idea. what a world. 02:45 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket 02:55 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 03:07 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket 03:43 < waxwing> i'm not sure about it myself. but an easy mistake to make is: it's not a PR for *using* fidelity bonds, only for adding the functionality to the wallet. 03:43 < waxwing> the thing i was always unsure about was the impact on anonymity. i can see various arguments around it. 04:01 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer] 04:11 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 04:45 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 246 seconds] 04:48 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #joinmarket 05:23 -!- Kelli44Koch [~Kelli44Ko@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds] 05:45 -!- DSRelBot [~DSRelBot@p54866D18.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 05:46 -!- HackRelay [~jmrelayha@p54866D18.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds] 06:01 -!- HackRelay [~jmrelayha@p54866910.dip0.t-ipconnect.de] has joined #joinmarket 06:04 -!- DSRelBot [~DSRelBot@p54866910.dip0.t-ipconnect.de] has joined #joinmarket 06:13 < belcher> adlai your view was that aged UTXOs should also be usable as fidelity bonds? 07:01 < belcher> regarding anonymity, id like to point out that any fidelity bond TXOs are not linked on-chain at all to coinjoins which are made, and that makers should be instructed to mix their coins before and after using them for fidelity bonds 08:34 < belcher> also another important thing with fidelity bonds that i dont talk about much: many makers today actually run multiple yield generator bots, because they make more money that way, that obviously seriously degrades privacy 08:34 < belcher> and fidelity bonds can fix it 08:35 < belcher> for years we've seen 4-5 bots on the irc channel connect and disconnect at the same time, clearly they're on the same internet connection.... and on the subreddit you occasionally get people admitting to running multiple bots (they seem to not know or care about the privacy implications) 08:56 < waxwing> yeah all fair points. there's more to say but we've discussed it before. 08:58 < belcher> yep 08:59 < belcher> btw, i now have a mastodon account https://x0f.org/@belcher 09:00 < waxwing> https://x0f.org/web/statuses/104111012928739572 09:00 < waxwing> then you saw that ^ :) 09:00 < waxwing> yeah i followed 09:01 < waxwing> it looks like it may be a bug, but the btcpayserver i connected to (owned by Kukks, the guy who did their impl.), sent back rbf-enabled inputs even though i sent our standard rbf-disabled ones. 09:02 < waxwing> so i just had the payjoin be rbf enabled with an extra flag to the tx constructor, which tbh we can probably do for all our direct sends (?) 09:04 < belcher> awesome 09:36 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 256 seconds] 09:46 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket 09:57 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #joinmarket 10:29 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.8] 10:44 -!- nixbitcoin_ is now known as nixbitcoin 12:41 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket 13:07 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds] 13:07 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds] 13:08 -!- jonatack [~jon@213.152.161.149] has joined #joinmarket 13:14 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket 13:39 < kristapsk> waxwing, about PRs I would like to see in 0.6.3 - #466, #523, #524, maybe also #567 13:40 < kristapsk> after 0.6.3 release I think it's good idea to also create python-3.5 branch, so that we can support it until EOL of python 3.5 and backport important bugfixes there 13:41 < kristapsk> and next major release could be 0.7.0 14:39 < waxwing> sounds good on the 3.5 branch 14:43 < waxwing> kristapsk, re PRs they all seem reasonable. can look at them over next week or so and try to get them in. 15:08 < belcher> i reviewed and tested #523 recently, i think it can be merged 15:37 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Executed for war crimes] 15:58 -!- jonatack [~jon@213.152.161.149] has quit [Ping timeout: 246 seconds] 16:00 -!- jonatack [~jon@37.167.8.190] has joined #joinmarket 17:39 -!- MaxSan [~four@185.156.175.171] has joined #joinmarket 17:50 -!- MaxSan [~four@185.156.175.171] has quit [Ping timeout: 246 seconds] 17:51 -!- HackRelay [~jmrelayha@p54866910.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 17:51 -!- DSRelBot [~DSRelBot@p54866910.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 18:03 -!- HackRelay [~jmrelayha@p5DE4A2DB.dip0.t-ipconnect.de] has joined #joinmarket 18:05 -!- DSRelBot [~DSRelBot@p5DE4A2DB.dip0.t-ipconnect.de] has joined #joinmarket 18:35 -!- HackRelay [~jmrelayha@p5DE4A2DB.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 18:36 -!- DSRelBot [~DSRelBot@p5DE4A2DB.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 18:47 -!- HackRelay [~jmrelayha@p5DE4A56A.dip0.t-ipconnect.de] has joined #joinmarket 18:50 -!- DSRelBot [~DSRelBot@p5DE4A56A.dip0.t-ipconnect.de] has joined #joinmarket 19:57 -!- chad2000 [daa64b0d@218-166-75-13.dynamic-ip.hinet.net] has joined #joinmarket 20:08 < chad2000> hello, I'm having trouble running the tumbler script. When running via tor it hangs on "Starting transaction monitor in wallet service, building irc'. When running it without tor it reports INFO:Commitment sourced OK, but then all the makers fail to respond. Any ideas on how I can troubleshoot this? I'm running without the GUI on Linux. 20:10 < chad2000> It also says INFO: Estimated miner/tx fees for this coinjoin amount for the whole tumbling run: 0.0%. That seems odd too 21:14 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds] 21:17 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket 21:28 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 21:29 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #joinmarket --- Log closed Tue May 05 00:00:11 2020