Teleport

There is the encapsulation of funds into a self-contained package (telepod) This is then sent and verified (cloned) so that the anon set is all the clonings during the specified timewindow (clonesmear)

However, different users have different clonesmear parameters so the attacker wont even know what the complete anon set is.

With the addition of even a small percentage of trusted teleports, the sender's anon set is the entire duration from the sender's cloning (when the funds were received) to when the destination account clones. this could literally be everybody as it is possible to age a telepod for months.

There are random delays wherever possible to make correlations difficult. Even the selection process of what telepods to use to fulfull a tx using a genetic algorithm that is based on evolution toward the best metric, but it is a stochastic process.

Each packet is put into L onion layers. The number of onion layers is randomized so it could be 1 layer or L.

The private nodes use probabilistic routing, or rather the network uses probabilistic routing to reach the private nodes. There is no (IP <-> acct) mapping, just a statistical histogram that each node that ever received a message from the private node maintains. For nodes that never received a direct message, there is no historical data to even look at. Each private node can determine what public nodes it announces itself to, and it will use its own loopback privacy server as a gateway to do this. It is possible that a determined attacker can do some brute force sybil attack to get a higher than noise level correlation of (IP <-> acct) so if you are really privacy minded, I would advise to NEVER publish your really private acct #. Only send this really private acct number to people you absolutely trust over the encrypted network. If the attacker doesnt know your acct #, then he cant run any sybil attacks to correlate it. Also, the longer the clonesmear window, the more private, so be patient and let time be your friend

Then there is the M of N fragmenting of each telepod with probabilistic dropout at each hop. What that means is that looking at packet traffic, it is quite difficult to know if a packet coming in was meant for that node, or whether it was dropped. Nor whether a packet coming out was originated from that node or just forwarded. When M packets arrive, the telepod is reassembled just like it was sent "directly"

As you can see Teleport is a bit more than "safely sending privkeys to transaction recipient"

James

P.S. ./BitcoinDarkd SuperNET '{"requestType":"sendmessage","dest":"13434315136155299987","msg":"hello"}'

The above is how to invoke the SuperNET API sendmessage command to send the message "hello" to dest acct 13434315136155299987