ANKRUSD
Ankr / United States dollar
crypto Composite

A shared cloud economy driven by idle processing power Ankr uses Cloud-Native, container-based environments to build its own architectural and resource allocation algorithm to include nearly all types of infrastructure resources. Cloud-Native allows Ankr to focus on its own technical details via integrating with various Cloud-Native solutions such as Observability & Analysis (Prometheus, Fluentd, Jaeger), Service Mesh and Discovery (Envoy, Istio), Streaming (GRPC), Application Definition (Helm) etc. Using Ankr's distributed cloud computing network (DCCN) platform, developers and operators using applications do not directly interact with infrastructure providers' API's. Instead, a local orchestrator handles resource allocation automatically. The Ankr DCCN system is deployed and distributed over the computing resources managed by Kubernetes across all geographic locations. Resources configured into clusters in Kubernetes are connected to each other via a specialized type of cluster called Ankr Hub. At this time Ankr Hubs are fully set up and controlled by Ankr and serve as nodes to relay and dispatch the computing tasks to other working clusters. Ankr's blockchain network is divided into four layers Core Layer: Full nodes use Proof of Service Level and Stake Byzantine Fault Tolerance, which defines the service quality of bandwidth, computation, and storing in the distributed cloud computing service market. Relay Layer: All nodes are full nodes but do not produce blocks or take part in consensus, rather they have the ability to add a better network on top of the layer, and can earn ANKR rewards based on proof of a network contribution (PNC). The PNC calculation is based on the node's relayed packet number, network steadiness, network bandwidth, and the node's quality of service. Access Layer: The access layer contains data center nodes, mining nodes, and edge computing nodes. All of these are light nodes and control illegal node access Micro-node Layer: The micro-node layer contains device nodes and transaction hashes. If a micro-node needs to retrieve network proof, it will ask the access-layer node. If the access-layer node can't provide a proof, the request will pass through the relay layer to the core layer.