Sentinel Documentation - #1 - Network Overview

Sentinel Documentation - #1 - Network Overview === Index === 1. Introduction 2. Definitions / Taxonomy - TBD 3. Overview of the Sentinel Network 1. Network Architecture 2. Public Networks 3. Private Networks 4. Node Types 5. Resources & Services Exchange 6. Zero Knowledge Exchange 7. Governance 1. Stateless 2. Session DAG with State Channel Progression 3. Eigen Trust and Reputation 8. Token Payouts and Exchange 1. Independent p2p Transactions 2. Recurring Pools 9. Workflows on Private Networks 10. Use Cases 1. Enterprise Operations 2. Community Management 3. The Ideal ICO (inspired from DAICO) Introduction === Sentinel is a decentralized network that facilitates the peer-to-peer exchange of computing resources such as bandwidth and storage (soon). Sentinel network currently monitors and measures bandwidth/data and the first utility developed using this protocol is the **Sentinel dVPN** (decentralized VPN) which demonstrates the utility of this protocol to provably exchange **bandwidth** with/without the *provider* having knowledge of the *consumer*. Each packet that flows through the Sentinel network will go through layers of encryption that is quantum-resistant (AES-256) or with even higher/lower grades of encryption, based on usage and utility. Architecture Overview === Sentinel's architecture is similar to a Hub & spoke model where the Hub handles network transactions (payments layer) while other Services (Sentinel dVPN, Sentinel dChat, etc.) operate out of a Zone. This model enables Sentinel's payments layer to be secure enough to handle transactions securely, while the Zone provides the requested Service. Sentinel's network in future will include other blockchains in Zones that are developed to work exclusively with the Sentinel Network either as Private Networks or Public Networks. ++More information on types of networks can be found here++ <diagram> with hub and zones with respective Validators and Delegators </diagram> In the above image, a user can observe that at the core of the Sentinel Network, lies the Hub, which is the single chain that'll handle transactions and validation required for the dVPN Zone. In future, with the Cosmos inter blockchain communication (Cosmos IBC) in place, the Hub & the Zone will be split up where the **Sentinel Hub** handles *payment transactions* alone and the **Sentinel dVPN Zone** will handle proofs of bandwidth exchange within the Zone. Overview of the Network === Sentinel Network comprises of the below layers: Layer 0 : Identity Layer governed by Reputation Layer 1 : Blockchain Layer with network consensus and finality Layer 2 : Resource Communication Layer with Payment Protocol using POST Layer 3 : Cognition Layer Layer 4 : Service Communication Layer - with application-specific logic using local DAGs or relational databases Layer 5 : Connectivity Layer - with protocols on alternative communication mediums (private mesh networks using radio) Layer 6 : Interactivity Layer - with ability to connect Services with interfaces like voice, virtual/augmented reality, etc. Layer 0 : Identity Layer - Anonymous User Identification Method === Sentinel’s unique zero-knowledge identity layer enables users to identify themselves to applications developed on the Sentinel Network and other integrations of Sentinel’s Identity Layer (AUID). This identity is governed by a multi-factor on-chain reputation that is algorithmically computed against each AUID. Every application developed on the Sentinel Network utilizes the network’s native authentication protocol/identity layer to give access to multiple users within the Sentinel Network - Public or Private Networks. Reference of identity is stored in a DAG that has reputation against it for accessing Services on the Sentinel Network. Sentinel Network’s Identity DAG is accessible by all Services and can be utilized by anyone creating Private Networks even within the Sentinel Network. An exclusive Identity DAG only for Private Nets can be developed and can be utilized within, completely independent of Sentinel Network’s Identity DAG or by connecting to it for computing User reputation from resource consumption within the entire Sentinel Network. This is primarily useful for Private Nets (or organizations/communities) that want to establish their own identity within the Private Net. Layer 1 : Blockchain Layer with network consensus and finality === Sentinel will have 3 DAGs running to support the network’s requirements of **Identity**, exchange of **Services** and related **Transactions**. Identity DAG --- This DAG stores all the required details of an identity, right from genesis to current state of reputation within the Sentinel Network. Identity DAGs maintained by Private Networks are independent of this DAG which will primarily utilize the consensus of Sentinel Network’s Identity DAG and not the store. This DAG serves as the reference for a the other identity DAGs operating on Sentinel Private Network. Reputation stored on this DAG is based on multiple factors on the Transactions DAG, rated by validators and Service Providers in the Service DAG. Service DAG --- A DAG with an index of Services connected to the Identity DAG serves as the layer Computed reputation is not the absolute indicator of Service offering, which depends on the last state of the User for a specific Service on the Sentinel Public Network or Transactions DAG --- All transactions in the Sentinel Network are stored within Discovery of Services within the Network === Currently, the Sentinel Network implementation utilizes a Node Resolver which is a type of Node that maps the ID of a Service Provider with the client of the Service Taxonomy === 1. **Sentinel or Sentinel Network** - a distributed and a decentralized network where *providers* exchange Services or Resources for *consumers* to consume/utilize 2. **Client** - the software that enables access to the Sentinel Network and access various features of the network like Account/Wallet Management, access network Services, etc. Clients can be for Desktop, Mobile, TV, VR devices, Smart Watches, etc. NOTE : Clients can be developed by anyone and will connect to the network and work exactly like an official release. Users are requested to make sure they trust the provider of the client (or at least cross verify) before downloading & using a Sentinel Network Client. 3. **Node** - a node is a part of the network that handles a specific function - either serving Clients or validating transactions or even maintain sync among the multiple chains that communicate between each other (after IBC or inter blockchain communication) The network currently has 2 types of Nodes - Validators (of the Sentinel Hub) and Service Nodes (for Sentinel dVPN, Sentinel dChat, etc.) 4. **Sentinel Public Network** - the network that is Public to everyone and currently, in this paper, it is only the official Sentinel Network. Here, the Sentinel Public Network is referred to as SPUN. 5. **Sentinel Private Network** - the network that is Private and is accessible only to authorized Clients with the ability to develop their own set of clients, nodes and possibly workflow rules based on the Sentinel Public Network. Here, the Sentinel Private Network is referred to as SPIN. 6. **Node Resolver** - the node responsible to map accounts of nodes of a specific Service or multiple Services with respective clients that configure the Node Resolver. By default Sentinel utilizes public Resolvers. Private Nets can either use their own Node Resolvers or can connect to the Sentinel Node Resolver Network. 7. **Service Node** - a node that hosts Services that can utilize a Public or a Private Network 8. **Resource Node** - a node that offers it’s resources (currently only bandwidth but will have compute and storage in future) 9. **Eigen Node** - a node that maintains trust between multiple types of nodes and contributes for the Reputation of various types of nodes within any network - Public or Private 10. **Gateway Nodes** - the node primarily enables discovery within the network and checks for available Service Nodes and syncs with the DAGs where Service Nodes, Resource Nodes, etc. register and declare themselves available* (to be confirmed) 11. **Sentinel dVPN Desktop Client** - the client that has the wallet integrated to access and pay for Resources and Services utilized using any of Windows, Mac OS or GNU/Linux (Debian and Ubuntu) 12. **Sentinel dVPN Lite Android App** - the Android app/client, available on Google Play, excludes the cryptocurrency wallet intentionally to enable users explore the technology without the barrier of understanding crypto as well. 13. **Sentinel dVPN** - the open-source client for Android available on the official GitHub repository. 14. **Sentinel Services or Sentinel dApps** - Applications that utilize the Sentinel Network (public or private) for either of networking or the payment protocols. 15. **Resources or Resources on the Sentinel Network** - Computing resources like Bandwidth, Storage and Compute that power the network or are contributed to the network’s Resource & Service Marketplace. 16. **Sentinel Network SDK** - a set of libraries that enable a developer to connect to the Sentinel Public Network (SPUN). This SDK (or a different release) will enable the creation of Private Networks (SPINs) and management of the same. 17. **Node Management Tools** - Tools that enable Node Hosts to manage various types of nodes hosted, related wallet configuration(s), payouts, resolve disputes, etc. 18. **Sentinel Utilities** - Tool Kits/Scripts/Applications put together by the Sentinel Community to contribute back to the community. 19. **Sentinel Service Network** - The marketplace to access various Services on the Sentinel Network.