00:59:26 <sgp_> Can we have a Bulletproofs+ meeting this week?
00:59:54 <sgp_> I'm busy until 2p ET though Wed
13:35:32 <Lyza> there's a little discussion on #monero about whether it would be good to, when an output age <10 blocks is selected as a decoy, choose 10 instead of re-rolling. The thinking is that there's going to be a non-smooth data point at age=10 because everyone who wants to send before that but can't, sends at 10 instead. more or less.
13:35:56 <Lyza> curious what the smarties over here have to say about it
13:40:26 <moneromooo> One possible niggle I see: the wallet only allows the tx to be made once an output is unlocked at 10. Then most get mined at 11, not 10.
13:40:52 <moneromooo> It'd certainly depend on how quick that next block comes.
13:47:27 <Lyza> so they can technically get mined at 10 but the official wallet won't allow it?
13:50:47 <Lyza> that would indeed be a niggle. might be a good move to make the wallet behavior & consensus requirements more in line if that's the case, but idk
14:01:02 <moneromooo> No. Most people won't make their tx a couple seconds after the 10th block. And even so, make a tx takes at least 10 seconds, then miners update their block template every 30 seconds, etc.
14:37:54 <Lyza> ok right of course, trying to think about how that would affect output selection but I don't quite see it
14:38:54 <Lyza> nope okay I see it. looking at the blockchain, the spends from age=10 are going to be distributed over a few blocks
17:05:27 <sgp_> moneromooo sarang: do you want to have a Bulletproofs+ meeting this Thursday?
17:07:58 <moneromooo> Not particularly. I can be there if someone wants me there though.
17:09:05 <sgp_> sarang says his work is almost done so it makes sense to have a convo on implementation I think
17:15:25 <dEBRUYNE> An audit is arguably required, especially given that sensitive parts of the code are touched
17:18:39 <sgp_> I want to ask Kraken to pay for the audit with their grant program
17:31:49 <sarang> An audit should absolutely happen
17:35:05 <sgp_> I know, but hat else needs to happen before it's added?
17:35:10 <sgp_> *what
17:37:21 <sarang> Logic for consensus rules, transaction format, etc.
17:37:35 <sarang> Similarly to how moneromooo did the initial BP changeover, I presume
17:38:38 <sgp_> is your code public yet sarang ?
17:38:54 <sarang> Yes
17:39:18 <sarang> https://github.com/SarangNoether/monero/tree/bp-plus
17:39:40 <sarang> I've been keeping it rebased
17:39:42 <sarang> and it passes CI