Will use Tor for transport between mixes. Pretty much like this: Users select a list of contacts for messages to go to, up to a certain number of contacts (probably thousands). The client automatically encrypts the message for each of the contacts, transparently to the client. The client automatically tags the message with a pairwise shared secret for each of the contacts. Client -> Tor -> Mix 1 -> Tor -> Mix 2 -> Tor -> Mix 3 -> Tor -> Encrypted Keyword Search Contacts periodically query the EKS server for the shared secret message tags, allowing them to get the messages from their contacts. The EKS server does not know which messages the contact searches for or which messages the contact obtains. Contact <-> Tor <-> Encrypted Keyword Search The EKS servers are a cluster that mirror each others content EKS1 <-> EKS2 <-> EKS3 <-> EKS4 <-> EKS5 Clients can connect to arbitrary EKS servers to obtain their messages, only one needs to be connected to at a time and they should be largely redundant. Clients sending forward messages can construct arbitrary mix pathes. Messages at mixes are alpha mixed giving clients the ability to select between anonymity and reliability. After a contacts client obtains a message, it automatically decrypts it, organizes it and displays it to the contact. The system can be used for private messaging, group private messaging more similar to chat, leaderless forum structures (which will essentially consist of several group private messages as threads, organized into forum structures client side by a set of rules the user makes) and blogs as well. Will probably have unlinkable contact strings as well as static strings for getting things like public blog pages, and probably even regular keyword search as well for finding arbitrary uploaded content. If you don't want to get messages from a person you can ignore them entirely and your client wont even download messages they tag for you. You also have total control in who can see the messages you send. If you send a message to people not ignoring you, everyone you select gets the message. Also plan to integrate something like Zerocoin if possible, originally the plan was to have code for centralized blind mixes and let people run them themselves but a distributed trustless blind mixing scheme is superior and Zerocoin has proven that this is possible. Control of Bitcoin will be totally integrated into the client, it will be as if you could click a Bitcoin button on the forum next to a persons avatar and select an amount of coins to send them, but also blinding will be integrated as well to make transactions totally unlinkable. All identities are authenticated and tied to ECDSA-384 keys, all messages are encrypted with ECDH-384 and AES-CTR-256 and all messages going through mixes are layer encrypted with LIONESS. So far the mixing part is done, Tor is interfaced with and networking code is done, the encryption is done and Bitcoin is interfaced with and the GUI is partially done. now it just needs somebody to implement the EKS algorithm, see if something like Zerocoin can be integrated to blind all Bitcoin transactions in a trustless way, and finish up the GUI and client side message sorting algorithms. The big advantage is that it is not for illegal activity. It is for whatever people want to use it for. It is not illegal to run EKS nodes or Mix nodes, and if people use them for illegal things well the people running the infrastructure cannot tell or stop them. Also taking down a single mix node or EKS node will have little to no effect on the ability of the users to continue to operate as before, provided there is a single EKS node and a single Mix node it is still possible to use the system. FBI has used attacks like that before against individuals but I don't think they ever did against so many people at the same time before.