MonkeyNet is just another Setup to remember.... When going into a place where you might encounter another Monkey with SECURE Comms capability, MonkeyNet Channel/Code is where you would do your initial Contact, and then mutually agree on another Channel/Code for Private Comms. Typically, You would use a MonkeyNet Symbolic, or ASCII One Time Operational PAD, to designate which Channel/Code Setup to use, thus eliminating any eavesdropping, while you do the initial Exchange. OpSec says if you are vetted into MonkeyNet, you would use one of the Universal Operational PADs, to make that initial Exchange. If either, or both, of the parties are NOT vetted into MonkeyNet, then you would need to make the initial Exchange in the clear, and take appropriate precautions, when doing the initial FaceMeet, as your initial Comms Setup, would NOT be SECURE, as well as the mutually agreed upon Channel/Code Setup. That is why vetting into MonkeyNet is important. It gives you access to the MonkeyNet Operational PADs required to make SECURE MonkeyNet Comms Exchanges, right off, rather than waiting to exchange a Mutually agreeable non-MonkeyNet PAD, during the FaceMeet. This is why we publish the technology for everyone, but keep the Distribution KeySets and PADs, and Operational KeySets and PADs, limited to vetted MonkeyNet Users. ANYONE can setup their OWN Mutually Agreeable PADs for use, anytime SECURE Comms are Needed, between two parties. They just have to use a common PAD, on both ends of the Comm Link. Now that the technology is well established Offshore, I can give the download URL, for the technology, to anyone who would like to get setup. This allows one to get to know the technology and use it for their own Private SECURE Comms, while still not compromising the MonkeyNet SECURE Comms System. How this all works, is explained n the MonkeyNet White Paper, available for download, in the Advanced Comms forum.