Like roads and kitchen knifes, apps that use cMixx can also be used for illicit activities.
In contrast to roads and knifes, the existence of cMixx can be counteracted easily. For example, if cMixx use grows over a certain threshold, it’s likely that parties like the EU will require regulation on the use of cMixx (and if this not happens, then they could forbid running nodes within the EU, or even using apps that use cMixx).
What is described below maybe a way to prevent the above from happening.
cMixx open/lite:
-
open to all developers to build into any app, no key required
-
makes apps big tech data mining proof
-
3 (and not 5 (as it is now)) nodes per round for higher speed, but still very secure, also against data mining by big tech
-
your digital life will not end in the ever growing big data pile that is out there
-
users of apps that use cMixx lite should be notified that when required by law the protected metadata may be revealed (users who don’t like this should not use the app), see the following 7 steps how the metadata in cMixx open/lite can be revealed if needed
(1) each round node software uses the “public key of the xx coin holders” to encrypt netflow and other metadata
(2) this data is synced over several or all the nodes and stored for a certain period of time
(3) the “private key of the xx coin holders” is stored on trusted hardware (HSM/TEE) and is under control of the council (chosen by the xx coin holders)
(4) in case of an LE request the council is able to get the specifically requested metadata to the requester, for example, 8 of 13 council members can reconstruct the treshold key that is required to decrypt the data
(5) the HSM decrypts, records audit log, signs audit log, sends decrypted metadata to the requester only
(6) the public can see the audit log (only append-able)
(7) the scripts and software required for steps 1-6, all open source
cMixx closed:
-
developers that wish to use cMixx closed need to apply for a key
-
xx coin holders decide who gets a key
-
in case of misuse of cMixx closed the key can be revoked
-
in cMixx closed netflow and other metadata will note be encrypted and stored as in cMixx open/lite, therefore the council cannot reveal any of the metadata; instead, regulation takes place by granting and, where applicable, revoking of the the required key in “cMixx closed”
-
cMixx closed has also 3 nodes per round, however, depending on the type of key applied for, it is possible to send a message in 2 or more consecutive rounds over “cMixx closed”, this makes is a bit slower, but it also makes it extremely unlikely that metadata will be found out by cooperating bad acting nodes, each extra consecutive round will also cost some extra xx coin