Some people asked for details of our plan and implementations, here are some information on it. I'll use question/answer format to give details. Please post more questions if you have, the dev team will do our best to answer them.
Q: What is the overall plan for SUPER to support anonymous features?
A: Our ultimate goal is to create a peer-to-peer and completely de-centralized anonymous system. This is shown in the following diagram. Any node can become an intermediate "mixing" node, if some minimum requirements are satisfied. There is no central control parts. Everything is peer-to-peer and de-centralized.
Remember that this is a trustless system, any node may cheat if it can.
In order to achieve this goal, we divide our work into 2 steps:
What is an anonymous system? Simply put, it is a system that people can not trace clearly the transactions from the blockchain, and see where the transaction really originated and where it is terminated. This protects people's privacy.
So why we don't go directly to our end-goal? This is because from our surveys and investigations, it is very complex and difficult to achieve a completely decentralized anonymous system. The key here is the "trust". When you do A->X->B, where X is some sort of the middle "mixer" node, the send or sign or commit of A->X and X->B (or its equivalent, such as a double-signed address, mini-escrow, etc), can not completely happen simultaneously, the one side (sender or Mixer-node) that has the last act can always cheat, though sometimes the cheat does not give the cheater benefits, but it can cause damage to the other party. Therefore, a complete trustless system is more difficult to be implemented (though it is possible - we'll discuss some more below).
For this reason, in phase-1 we decided to develop a system that will depend on some sort of the trust, it is much easier to implement, and will give people the anonymous feature. This trust will be done through the dev team, or a credible mining pool.
Q: So what is your Phase-1 solution?
A: Our initial anon solution will involve some middle trusted mixing pools. This is shown in the following diagram:
The mixing pools will be hosted initially by dev team, and can also be hosted by credible mining pools. The anon send will be directed to these mixing pools by wallet and mixed and then send to its destination.
Basically it is done like this:
A (source) -> {Xi} (i = 1, ..., m), then {Yi} (i = 1, ..., n)->B (destination)
where {Xi} and {Yi} are randomly chosen addresses from a large pool of addresses (belonging to a mixing pool,
and these addresses are periodically refreshed, phased out, and created).
The source amount from A is split randomly into m parts (for now we choose m = 2,3 or 4 randomly in the anon version we will release for testing, but it will be a configurable parameters later), they are sent to m random addresses in randomly chosen mixing pool. The pool, on confirming the amounts received, will send the same amount in n parts to the destination (for our testnet we choose n=1, again this can be changed and configured). The result transaction is not traceable (at least extremely difficult to trace, given the large number of addresses in the mixing pool and dynamism of the addresses).
The main part of our phase-1 solution is implemented, and we will release a version for testnet shortly.
Q: Sounds good, is mixing pool software and coin wallet client are two different software?
A: Absolutely not. They are exactly the same. It is the SUPER coin wallet. Eventually this will be used for peer-to-peer system (in phase-2), so no reason to be different. Now we configure only a few special nodes as trusted nodes. Once we implement the trustless system in phase-2, no special config is needed.
Q: What is a trust system, and what is a trustless system?
A: A trust system will have at least one node that everyone trusts. This node will never cheat. Other nodes may or may not cheat.
A trustless system is that any nodes will cheat if they can. So to implement a trustless system it is more difficult as you have to implement mechanisms to prevent or discourage a node to cheat. If a node cheats, it will lose much more than it gains.
Q: Can you give some details on the mixing pool?
A: OK, it is basically a wallet client, with a pool feature configured as shown below.
A array of the incoming/outgoing addresses are created and refreshed dynamically, and randomly chosen for each transaction. Incoming and outgoing addresses balance their coins with predefined algorithms.
Q: Looks good for Phase-1. What about Phase-2? Is it feasible?
A: Phase-2 is absolutely feasible, albeit more difficult. We actually already defined a workable scheme, and work on
details now. It involves a complex system with multi-signature (m-to-n signature) addresses and multi-signature transactions. We can not reveal more details now. We will publish the full scheme design details after we implement, test and release it.
The Phase-2 will be built on top of the Phase-1 codebase. In phase-2, any node (wallet client) can become an intermediate mixing node if it satisfy some minimum requirements (e.g. minimum balance, network connectivity etc).
Q: What is the overall plan for SUPER to support anonymous features?
A: Our ultimate goal is to create a peer-to-peer and completely de-centralized anonymous system. This is shown in the following diagram. Any node can become an intermediate "mixing" node, if some minimum requirements are satisfied. There is no central control parts. Everything is peer-to-peer and de-centralized.
Remember that this is a trustless system, any node may cheat if it can.
In order to achieve this goal, we divide our work into 2 steps:
- Phase-1. To achieve anonymous wallet with a simplified, and easy to implement system
- Phase-2. To implement a fully de-centralized peer-to-peer anonymous system
What is an anonymous system? Simply put, it is a system that people can not trace clearly the transactions from the blockchain, and see where the transaction really originated and where it is terminated. This protects people's privacy.
So why we don't go directly to our end-goal? This is because from our surveys and investigations, it is very complex and difficult to achieve a completely decentralized anonymous system. The key here is the "trust". When you do A->X->B, where X is some sort of the middle "mixer" node, the send or sign or commit of A->X and X->B (or its equivalent, such as a double-signed address, mini-escrow, etc), can not completely happen simultaneously, the one side (sender or Mixer-node) that has the last act can always cheat, though sometimes the cheat does not give the cheater benefits, but it can cause damage to the other party. Therefore, a complete trustless system is more difficult to be implemented (though it is possible - we'll discuss some more below).
For this reason, in phase-1 we decided to develop a system that will depend on some sort of the trust, it is much easier to implement, and will give people the anonymous feature. This trust will be done through the dev team, or a credible mining pool.
Q: So what is your Phase-1 solution?
A: Our initial anon solution will involve some middle trusted mixing pools. This is shown in the following diagram:
The mixing pools will be hosted initially by dev team, and can also be hosted by credible mining pools. The anon send will be directed to these mixing pools by wallet and mixed and then send to its destination.
Basically it is done like this:
A (source) -> {Xi} (i = 1, ..., m), then {Yi} (i = 1, ..., n)->B (destination)
where {Xi} and {Yi} are randomly chosen addresses from a large pool of addresses (belonging to a mixing pool,
and these addresses are periodically refreshed, phased out, and created).
The source amount from A is split randomly into m parts (for now we choose m = 2,3 or 4 randomly in the anon version we will release for testing, but it will be a configurable parameters later), they are sent to m random addresses in randomly chosen mixing pool. The pool, on confirming the amounts received, will send the same amount in n parts to the destination (for our testnet we choose n=1, again this can be changed and configured). The result transaction is not traceable (at least extremely difficult to trace, given the large number of addresses in the mixing pool and dynamism of the addresses).
The main part of our phase-1 solution is implemented, and we will release a version for testnet shortly.
Q: Sounds good, is mixing pool software and coin wallet client are two different software?
A: Absolutely not. They are exactly the same. It is the SUPER coin wallet. Eventually this will be used for peer-to-peer system (in phase-2), so no reason to be different. Now we configure only a few special nodes as trusted nodes. Once we implement the trustless system in phase-2, no special config is needed.
Q: What is a trust system, and what is a trustless system?
A: A trust system will have at least one node that everyone trusts. This node will never cheat. Other nodes may or may not cheat.
A trustless system is that any nodes will cheat if they can. So to implement a trustless system it is more difficult as you have to implement mechanisms to prevent or discourage a node to cheat. If a node cheats, it will lose much more than it gains.
Q: Can you give some details on the mixing pool?
A: OK, it is basically a wallet client, with a pool feature configured as shown below.
A array of the incoming/outgoing addresses are created and refreshed dynamically, and randomly chosen for each transaction. Incoming and outgoing addresses balance their coins with predefined algorithms.
Q: Looks good for Phase-1. What about Phase-2? Is it feasible?
A: Phase-2 is absolutely feasible, albeit more difficult. We actually already defined a workable scheme, and work on
details now. It involves a complex system with multi-signature (m-to-n signature) addresses and multi-signature transactions. We can not reveal more details now. We will publish the full scheme design details after we implement, test and release it.
The Phase-2 will be built on top of the Phase-1 codebase. In phase-2, any node (wallet client) can become an intermediate mixing node if it satisfy some minimum requirements (e.g. minimum balance, network connectivity etc).
Excellent description, very knowledgeable dev!
/0.018$???
