Reputation Infrastructure and Ecosystem
As provided in NuNet Whitepaper 2.0 (see [PDF edition page 31](https://nunet-io.github.io/public/NuNet_Whitepaper_2.0.pdf) or [direct link to online edition](https://docs.nunet.io/nunet-whitepaper/governance-and-decentralization/future-nunet-token)), NuNet platform will provide *reputation infrastructure* (mostly via Tokenomics and Reputation APIs) for reputation ecosystem: > A reputation system which will provide a basis for informal and community ecosystem driven verification, validation and trust of supply-side service providers. NuNet framework will provide guaranteed general mechanisms and information flows (Reputation API and Telemetry API) needed for reputation systems and their algorithms. Initially, NuNet will build a prototypical reputation system for bootstrapping the network operation; in the long term, however, the framework will encourage third party AI service providers to implement competing reputation systems as network operations agents and compete for best and most reliable reputation services -- eventually leading to a dynamically evolving reputation ecosystem. Based on that and in line with the use-case based platform development model, we will develop NuNet's **reputation system** on top of that infrastructure. Note the crucial difference and relation between *ecosystem* and *system*: **an ecosystem is a multiplicity of reputation systems**. Our goal is to bootstrap the reputation ecosystem by creating infrastructure and providing (minimal viable) implementation of NuNet's reputation system. It is important that both are created together. 1. **Reputation infrastructure** is: 1. Subset of Telemetry, Tokenomics and other APIs of NuNet platform which enable components of the platform to share information about their performance and reputation systems to be able to consume this information and build their own logic; 2. A unified reputation API which enables other components of the platform to query any reputation system for required information; This is related to implementation of Elastic stack (https://gitlab.com/nunet/architecture/-/issues/132) as a part of the Telemetry data acquisition and observability epic (https://gitlab.com/groups/nunet/-/epics/43) 3. Since Open API is covered by Licence Regime 1, reputation infrastructure is also covered by Licence Regime 1, which AGPL -- and is part of the platform core; 2. NuNet **reputation system** implementation provides a minimally valuable implementation of a reputation system enabled by the above infrastructure: 1. Concrete algorithms according to which a reputation system will provide information about component behaviour (SPD, etc); 2. NuNet reputation system shall be covered by Licensing Regime 2, thus Apache 2.0; It is non-core platform components, which can be implemented by third parties. Eventually, each component will be able to choose the reputation system to rely upon;
epic