Why Parsec rather than SSL/TLS?

The new generation of digital looters uses the US-based local business to “legally” loot domains in any non-US zones, including “sovereign” zones like .io. The scheme is quite simple: US judge can and do (we have a record of such decisions) decide that some domain in foreign zone should be owned by a local US-based business, and having such judgement ICANN (or the appropriate domain zone authorities) will just transfer your domain to a looter without even letting your registrar know what’s happening. Then, the new SSL certificate is issued normally, and your users will even not known that their data are being “legally” phished by somebody.

Also, there are, frankly, practically zero chances for a foreign business to win a battle agains a local one in US court, and any decisions in the international courts are either just ignored or ignored with sanctions imposed to the judges to its stuff (see, for example, The US has imposed sanctions on senior officials in the International Criminal Court (ICC), including chief prosecutor Fatou Bensouda.

Therefore, the only way to build a service not prone for blackmailing, stealing or, worse of all, transparently attacked and compromised, is not to use neither DNS nor SSL/TLS at all. Only this is the way when you can really own your domains (your primary Internet property), rather than lease it from the US-controlled centralized services.

This is where Parsec comes to a help. UNS2 (parsec 1.3) allow your service to be connected (without DNS involved) to the direct IP addresses that are not controlled from US grounds, this way effectively ignoring any US-territory based attack; and Parsec 1.1 and 1.2 allow to use pre-shared IP address and Universa network to check the authenticity of the service on these IPs.

Parsec libraries and standards, as with Universa sources, are open source and available for public for free; UNS2 contracts, which are network-stored, are available at a minimum price that covers the network processing and storage expenses.

See parsec.1 specifications for more on Parsec versions and implementation.