Composable DHT Naming

Multiple names are required in order to distinguish the different concepts introduced. The following are the current candidates:

Omnidex - the name of the overall composable DHT concept where multiple DHT features co-exist in the same network. If this concept gets published, the same name would be used as title of the paper. See OmniDex (Composable DHT) for more detail.
Omninet - the public common good network composed of peers adhering to the Omnidex conventions that we’d expect many libp2p applications to use by default.
IPHT 1.0 - the name for the IPFS blueprint. This is versioned as it is expected to evolve over time. A blueprint encapsulates the suite of features endorsed by specific software or a collective of peers. IPHT would therefore consist of (1) Peer Routing, (2) Provider Records, and (3) IPNS.
Amino - the name for the swarm of peers that implement IPHT and consequently are part of the Omninet. This has traditionally been referred to as the “public IPFS DHT” using the libp2p protocol id /ipfs/kad/1.0.0.

Some English usage examples:

Providing CIDs to Amino takes less than a second
Kubo looks up the CID in Amino to find the content
Kubo supports IPHT 1.0 so any Kubo node can join Amino
Nodes participating in Amino are also discoverable by other nodes in the Omninet because they all support the Omnidex rules for populating routing tables.

In terms of the repositories, we propose the following naming conventions:

Names that were considered

Composable DHT: modular and flexible DHT.
NexaNet: A play on the word “nexus,” meaning a connection or series of connections, combined with “net” for network.
ExoDex: Exo- refers to “outside” or “external” and -dex is derived from “index”. ExoDex is a global index, external to any entity by its decentralized nature.
ExoNet: Signifying a network that reaches the outer limits, from the word “exosphere.”
OmniRoute: Emphasizing the idea of universal routing capabilities.