Platform component classes

NuNet framework consists of three component classes:

1. Core Platform Components

This is platform code that has to be used by all stakeholders of the framework in order to use the platform and cannot be duplicated – therefore have to be shared. As the name indicates, the code that constitutes these components makes the platform a platform. These include, but not limited to communication protocols, application programming interfaces (APIs), software development kits (SDKs), encryption mechanisms, blockchain integrations (smart contracts), transaction settling mechanisms (NTX token), network tokenomics.

2. Non-core Platform Components

These are platform components and code that are still needed for the platform to function, but the ones that can be duplicated / operate concurrently within the platform and therefore the development of these components can be decentralized. These components include network operating agents (as called in the original Whitepaper), which will provide capabilities and AI services for managing the network, reputation systems, oracles (for compute verification), developer tooling (development and debugging frameworks for building on NuNet) etc. Currently (and in the foreseeable future) NuNet is building these components as they are needed for the platform to function properly. The long term goal, however, is to to build the core platform components (most importantly APIs, SDKs and blockchain integrations) in a way that enables community developers to compete in developing (and possibly monetizing via NuNet network tokenomics) non-core platform components and run them concurrently on the platform – allowing users to choose their preferred network operating agents, reputation systems and oracles.

3. Use-case applications and IP protected components

The medium-to-long term goal of platform development is to reach the tipping point, when third parties are able to successfully execute the IT part of their business models on NuNet platform without NuNet’s development teams' contribution (save for support services). However, due to reasons explained in the section on our use-case based platform development model, NuNet core developers team is building use-case applications in order to reach that tipping point. Nevertheless, these components should be properly licensed and separated from the core platform code, which will become more important when we will attract different business usages and parties (see business development section).