-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPoSe Movement #2 - Proposing Changes in Mixin #95
Comments
Like Where is Wally? |
I don't know if that would be to much but what's about analyzing the data from the past and create the outputs by AI, just as an idea. |
This change is based on individual chain's historical data, an adaptive approach. It is done at the code level. So you are on the right track. Statistics use existing data. |
DB on our block data is required to proceed further. |
Will reopen this issue if necessary. |
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?
The text was updated successfully, but these errors were encountered: