There are two types of DNet nodes: DNetcoin & Overlay App. App has Overlay Cloud (OVC) and Client.
The following four types of nodes can run within one program or separately.
DNetcoin node is the full node to store and run the blockchain. The blockchain nodes process transactions and mine for new blocks. The blockchain node usually runs on data center with public IP address and stays on-line 24x7. This type of node is completely open and no private information stored.
The nodes to run the computing for block generation. The security requirement is the coinbase generation and the coinbase's output address should belong to the miner.
ĐNET token wallet is the application to create token transactions using the wallet's private key. The transactions are then sent to blockchain nodes for processing. It is similar to Bitcoin wallet. This wallet node usually runs on private computer and goes online when needed.
This type of node needs access owner's private key and should be highly secured environment.
DBA node is responsible to perform DNetDB write operations. It uses private key to the sign the UTXO to create psuedo token transactions. Such psuedo transactions are the DNetDB's create, write and update operation logs, similar to database's SQL logs. Such logs are stored on blockchain along with the token transaction ledger. Both the dnet and ovc data are managed on the DBA node. This DBA node usually runs on private computer and goes online only when modifying the DNetDB.
This type of node needs access DBA's private key and should be highly secured environment.
The application node is the other side of the node which reads from DNetDB. The application nodes only need the block headers to verify the DNetDB data with Merkle proof algorithm. Both the App and OVC nodes use the retrieved and parsed blockdata to configure and drive the application specific logics.
The DNet App Driver is the bridge in-between and maps the states in blockchain to the states in applications. The "copy-n-paste" process is tamper-proof and guarded by Merkle Proof algorithm.
The Tinc VPN nodes connect with each other to form a Layer 3 fully meshed overlay network and standard TCP/IP applications can run on this virtual overlay network.
Each node is identified by its virtual IP address and PubKey, and both are stored on blockchain as an entry on
Overlay Cloud(OVC) node acts as the name indicated and serves as the cloud backend for the application. For the Tinc VPN app, the OVC is the connection broker and traffic relay node for peer Tinc VPN nodes. Be more specific, the peer nodes have a
connectTo = 'OVC_PUBLIC_IP' configuration item pointing to the OVC node. The
'OVC_PUBLIC_IP' is retrieved from blockchain.
'OVC_PUBLIC_IP' can also be a domain name, either static or Dynamic DNS.
The other key information retrieved from blockchain is the OVC node's public key, which is the used to encrypted message sent to the OVC node.