Skip to content
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

Open
Xecute0101 opened this issue Jun 15, 2019 · 4 comments
Open

EPoSe Movement #2 - Proposing Changes in Mixin #95

Xecute0101 opened this issue Jun 15, 2019 · 4 comments

Comments

@Xecute0101
Copy link
Contributor

@Xecute0101 Xecute0101 commented Jun 15, 2019

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.

1

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.

2

When high mixin is selected, outputs with most population in each digit is used to create txs and vice versa.

Any thoughts, guys?

@Xecute0101

This comment has been minimized.

Copy link
Contributor Author

@Xecute0101 Xecute0101 commented Jun 17, 2019

Like Where is Wally?

@exploshot

This comment has been minimized.

Copy link
Member

@exploshot exploshot commented Jun 17, 2019

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.

@Xecute0101

This comment has been minimized.

Copy link
Contributor Author

@Xecute0101 Xecute0101 commented Jun 17, 2019

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.

@Xecute0101

This comment has been minimized.

Copy link
Contributor Author

@Xecute0101 Xecute0101 commented Jul 15, 2019

DB on our block data is required to proceed further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.