Prerequisite: DB Implementation
Instead of utilizing ring confidential transaction (hiding information),
We should think about using statistics to make it more difficult to trace and pinpoint txs.

Here we see the pretty amounts for making outputs. From our blockchain history, the chain can analyze the population of each output in each digit space (statistical term). If conventional mixin focuses on mixing sudo and real inputs to obfuscate real outputs. What I am suggesting is to populate certain outputs so that their population grows over time and tracing txs more difficult because they all look the same or alike.

When high mixin is selected, outputs with most population in each digit is used to create txs and vice versa.
Any thoughts, guys?
Prerequisite: DB Implementation
Instead of utilizing ring confidential transaction (hiding information),
We should think about using statistics to make it more difficult to trace and pinpoint txs.
Here we see the pretty amounts for making outputs. From our blockchain history, the chain can analyze the population of each output in each digit space (statistical term). If conventional mixin focuses on mixing sudo and real inputs to obfuscate real outputs. What I am suggesting is to populate certain outputs so that their population grows over time and tracing txs more difficult because they all look the same or alike.
When high mixin is selected, outputs with most population in each digit is used to create txs and vice versa.
Any thoughts, guys?