Can we have a Bulletproofs+ meeting this week?

I'm busy until 2p ET though Wed

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.

curious what the smarties over here have to say about it

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.

It'd certainly depend on how quick that next block comes.

so they can technically get mined at 10 but the official wallet won't allow it?

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

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.

ok right of course, trying to think about how that would affect output selection but I don't quite see it

nope okay I see it. looking at the blockchain, the spends from age=10 are going to be distributed over a few blocks

moneromooo sarang: do you want to have a Bulletproofs+ meeting this Thursday?

Not particularly. I can be there if someone wants me there though.

sarang says his work is almost done so it makes sense to have a convo on implementation I think

An audit is arguably required, especially given that sensitive parts of the code are touched

I want to ask Kraken to pay for the audit with their grant program

An audit should absolutely happen

I know, but hat else needs to happen before it's added?

*what

Logic for consensus rules, transaction format, etc.

Similarly to how moneromooo did the initial BP changeover, I presume

is your code public yet sarang ?

Yes

I've been keeping it rebased

and it passes CI