NESS NODE

Conception

There are two main parts of the system:

• The server part (Node)
• The user part (Local)

Node

The node part is maximun-lightweight and it consists of services.
Each node is recorded inside blockchain and can have it’s owner (optional) and hub (optional)

Node Blockchain record

• type — type of node, in our case “ness”
• url — URL of node
• nonce — random text
• tags — tags to be used to catalogise and find the node (optional)
• hub — collection of nodes (optional)
  hub.blockchain.nvs.name
• hub-sig — signature wich shows that this current node belongs to the current hub
  sing(hub.blockchain.nvs.privkey, node.blockchain.nvs.name)
• owner — owner of he node (optional)
  owner.blockchain.nvs.name
• owner-sig — signature wich shows that this current node belongs to the current owner
  sing(owner.blockchain.nvs.privkey , node.blockchain.nvs.name)
• dpo — emercoin Digital Proove of Ownership
  dpo.blockchain.nvs.name
• dpo-sig — sing(dpo.blockchain.nvs.privkey, node.blockchain.nvs.name)

WORM

<!-- First two levels of tags are standardised -->
<worm>
<node type=”ness” url=”127.0.0.1” nonce=”w9gjejg7jgk” tags=”video,streaming”>
<!-- Here tags may be different for each type of node or each node --> </node>
</worm>

Service

The service is a simple program or driver, which performs one single action.
The main service is node service. It shows the current information about the node and other info:

• Node load state
• The node list (from blockchain)
• The hub list (from blockchain)
• The current hub and node list from current hub (from blockchain)
• The service list from this current node