V9 Ringsize #11

What should the ringsize for the next hard fork be?

Monero is considering doing static ringsize 11 and switching to a per byte fee. See https://docs.google.com/document/d/1Y3IsjH7ywJOvFeZd1qT1fRfz2lw8APp8ptcyDXzYrxk/edit from ArticMine.

There is no practical difference between ringsize 10 and 11:

I am not aware of any specific improvements that a larger ringsize would provide. Of course bigger is strictly better, but ideally any recommendations would be grounded in specific threat-models.

Surae Noether speaking about potential ringsizes for Monero:

We might be able to get up to ringsizes 16 or 17 or something like that...

Also:

I don't know... there's also an argument to be made based on some of these formulas that I'm looking at that it's possible that I can look at the point at which the gain is negligible and then maybe I can be like 'once we're past 22 we can just call it quits.' And if we can get up to 22, that's so close to 7 right now. For triple our current verification time, we can just call it quits for ringsize forever? Like really? I mean that's tempting to me. But if I said that out loud smooth (a Monero Core Team member) would start yelling at me about costs to blockchain. But Aeon coin can do what they want and we can do what we want.

I unfortunately do not have access to the formulas he is referring to.

In any case, I strongly recommend a fixed ringsize for nearly any size >2.

22 then?

22

so much privacy

The masses have spoken... 22 it is.