%25E5%25B9%25A3%2520logo_%25E5%25B7%25A5%25E4%25BD%259C%25E5%258D%2580%25E5%259F%259F%25201.png%3Falt%3Dmedia%26token%3Dd68ceeea-55fe-400d-86bb-8e7d64a75e30)
%25E5%25B9%25A3%2520logo_%25E5%25B7%25A5%25E4%25BD%259C%25E5%258D%2580%25E5%259F%259F%25201.png%3Falt%3Dmedia%26token%3Dd68ceeea-55fe-400d-86bb-8e7d64a75e30)
Coordinating Node Model
Spiderweb has developed three types of node roles with different specifications and functions that can be interactively collaborated to meet server demands.
Spiderweb Three Node Types
As the main parts of Decentralized IDC (D.I.D.C.) architecture, Spiderweb provides traditional online service provider (OSP) clients a solution to quickly and conveniently convert and deploy their online application services to decentralized blockchain scenarios while incorporating several active and passive security protection mechanisms to protect data.
Since enterprise clients have high requirements on the quality of blockchain services and need absolute Internet connection stability, and at the same time have more concerns about using external blockchain public chains, most enterprise clients need Private Node deployment as node resources.
All Spiderweb Verification Nodes serve as a public chain node resource for Blockchain Technology Provider (BSP) clients in the Spiderweb Network ecosystem, used to store Ledger data for them.
Last modified 1yr ago