Sentinel Sync & Resolver Nodes === Sync Nodes (or Full Nodes) --- ### Overview - Sync Nodes download the data of the chain (or sync the chain) to enable access to required nodes within/outside (TBD) the network. - This prevents validators from being exposed to other nodes on the network - Sync Nodes need no reputation to start running on the network - Sync Nodes work with multiple chains within the network ### Node Setup & Configuration - Configuration : 4 core, 8GB RAM, 20GB SSD - Resolver Nodes --- *(currently for Sentinel dVPN on the root chain and in future the Sentinel dVPN Zone)* ### Overview - Resolver Nodes in the Sentinel network handle resolution of the Node ID to the IP. - Each node is independent of other Resolver nodes in the network - Each Resolver Node connects to their own Sync Nodes (TBD) to get data of Service Provider Registrations. - Each RN can be configured by a pre-defined/unlimited (TBD) number of clients that configure a Resolver Node with it's ID (TBD) - To prevent bad actors, the Resolver will need Reputation to be a part of the network (Ex: run Sync Node and have an uptime of a min. of 100 days). In future the selection might move to a more authoritative PoA (Proof of Authority) system (TBD) #### Use in Private Networks - Resolver Nodes can be configured by independent enterprises/organizations for providing exclusive access to self-hosted nodes ### Node Setup & Configuration - Configuration : 4 core, 8-16GB RAM, 50GB SSD - ### Network Diagram