... the AEON approach of allowing limited use of 0 mix and non-RingCT transactions would allow things like pool payouts where both tracing and hiding amounts is largely pointless (the blocks mined by the pool is generally public anyway, as are the payout transactions) to be done with lower cost. Or at least, they would bid for access to the quota of 0-mix transactions. My guess is that those slots would be most valuable to pools for cheap payouts, but I don't know. The market will sort it out.
I don't see RingCT or required mixing being a problem here at all. People who don't need it can opt out, as long as is kept under control and doesn't compromise the privacy of the chain as a whole...
Hey Smooth, is there somewhere I can read more about what the AEON approach is concerning allowing a limited number of 0 mix and non RCT tx's without compromising the overall privacy of the chain as a whole?
Obviously including a 0 mix input into a >1 mix reduces privacy at the most basic level. Is there already/will there be an algo that is used to regulate this ?
Thanks
There are two methods planned, one of which is already implemented in the current release. The first (already implemented) is that the number of 0-mix (also currently 1-mix, but maybe those should be prohibited altogether) transactions is limited to a maximum of one per block. Given growth in usage that will be a small minority of the total number of transactions, which results, statistically, in the chain as a whole is being protected any sort of chain reaction attacks.
The second method allowing a different pathway for smaller and lower-cost transactions is planned for an upcoming upgrade but has not been disclosed yet.