00:06:52 <selsta> luigi1111: please merge the merge list early, it contains trivial patches that fix compile related regression
00:08:34 <luigi1111> ok
00:14:13 <chad[m]> W.r.t. the recent privacy bug for wallets spending a TX at exactly 10 block age: as anyone done an analysis on the effects on neighboring transactions? For example, if one of the decoys in my transaction were spent elsewhere at exactly 10 blocks, it would be trivial to show that it was spent elsewhere, and therefore only a decoy in my TX; thus... my privacy is reduced, even though I waited longer than 10 blocks to spend
00:15:41 <chad[m]> I'd be curious to know:
00:15:41 <chad[m]> 1) how many TXs were spent with 0 privacy (e.g. this bug)
00:15:41 <chad[m]> 2) how many other TXs used those 0-privacy outputs as decoys
00:16:26 <sethsimmons> > <@chad:monero.social> I'd be curious to know:
00:16:26 <sethsimmons> > 1) how many TXs were spent with 0 privacy (e.g. this bug)
00:16:26 <sethsimmons> > 2) how many other TXs used those 0-privacy outputs as decoys
00:16:26 <sethsimmons> https://github.com/monero-project/monero/issues/7807#issuecomment-887214798
00:17:01 <sethsimmons> Even with the bug you can't know for certain if its true spend or decoy, it just makes the guesses more likely to be correct.
00:17:33 <sethsimmons> It seems there is very little chance it has a snowballing effect on privacy due to how few of these situations occurred.
00:21:34 <chad[m]> This:
00:21:34 <chad[m]> > The decoy selection algorithm has next to 0 chance of selecting extremely recent outputs as decoys.
00:21:34 <chad[m]> Contradicts this:
00:21:34 <chad[m]> > only ~1% of outputs used in rings were between 10 and 12 blocks old, and a percentage of those were likely decoys
00:22:12 <chad[m]> A next to 0 percentage were likely decoys. More likely >99% of them were real spends
00:25:42 <chad[m]> If 1% of outputs were exposed because of this issue, wouldn't this mean 1% of decoys in other transactions used one of these 0-privacy outputs?
00:26:43 <sethsimmons> That would be the absolute maximum but likely less depending on timing of those transactions due to the decoy selection algo.
00:28:19 <sethsimmons> Also, 1% of decoys, if affected and known, would mean 1 decoy out of 10  transactions would be able to be discounted, so practically no impact to users who aren't directly affected by the bug.
00:29:02 <sethsimmons> But yes, 1% is still not 0%.
00:29:02 <sethsimmons> The real world impact on those not directly affected by the bug is still practically none, IMO.
00:29:25 <chad[m]> Gotcha. Thanks, that's what I was trying to understand
00:31:20 <chad[m]> With my luck, I probably picked 11/11 shit decoys ;)
00:37:00 <sethsimmons> <chad[m] "With my luck, I probably picked "> That would be one hell of a bad ring 😂
10:28:47 <john_alan> @moneromoooo: are you still working part time paid on Monero or back to voluntary contributions?
10:31:35 <moneromoooo> I still have a ffs going, slowly.
10:43:23 <doser[m]> hi all. Am new to monero. 
10:43:30 <doser[m]> Is there a mobile wallet that I can connect with my node?
10:43:41 <doser[m]> so like Ligtning Nwtwork does it over Onion
10:45:27 <moneromoooo> Try asking in #monero, they should know.
11:33:59 <john_alan> Ok cool so you’re still interested in paid woeking
11:34:02 <john_alan> Working *
11:35:13 <john_alan> I can’t see it in funding required moneromoooo
11:35:23 <john_alan> https://ccs.getmonero.org/funding-required/
11:36:56 <moneromoooo> https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/192
11:57:41 <plowsof[m]> Welcome! https://www.getmonero.org/ is a better place to start your journey.
12:19:33 <john_alan> Awesome thanks moo
18:00:59 <luigi1111w> .merges
18:01:00 -xmr-pr- 7813 7814 7815