DNet Management

Create DNet ('mydnet')

The 'mydnet' is symbolic only and can be the same, while the dnet id is unique and locked by the wallet's private key and no one else can manage it.

create-mydnet

Add Member Node

The node's cryto ID, a.k.a c2pkh, is obtained from the node's owner (see how). The dnet admin needs to assign an unique virtual IP address. For simplicity, the uniqueness is within the scope of this dnet.

add-node

Add Overlay Cloud

add-ovc

Overlay Cloud (OVC) can be from (what is OVC?):

  • public OVC, e.g. a working OVC_ID for testdnet is xxxxxxxxxxxxxxx, this is the default setting, more...
  • private OVC, created by self (see how);
  • third party OVC provided as a paid service, the service can be paid with DNC token, or BTC/ETC etc crypto currencies or standard credit cards.

Using Public OVC nodes, the dnet is multi-tenanted with other dnets, while using the private OVC nodes, only multi-tenanted with self dnets.

Add Overlay Relay

add-ovr

Overlay Relay (OVR) can be from (what is OVR?):

  • private OVR, created by self (see how);
  • provided by third party as a paid service, the service can be paid with DNC token, or BTC/ETC/SOL etc crypto currencies or standard credit cards.

Edit this page on GitHub