High Performance and Reliable RPC Services for Aptos
BlockPI is a decentralized cross-chain interoperable service network for Web3.0 developers.
BlockPI Network aims to provide high-quality, robust, and efficient RPC service. To avoid the single-point failure and limitation of scalability, the network is designed to be a distributed structure with expandable working nodes. This page introduces the detailed roles and the service mechanisms of the BlockPI Network.
BlockPI Hub is a server managing the user system, node rating and authenticator system, and accounting system. The user’s registration information, account information, and KYC information are maintained here. It also tests the nodes in the network all the time and gives them scores which is a source of BlockPI Load Balancer. The income and expenses of the entire network are calculated here, as well as the rewards issued to characters in the system. As you can see, this part is a centralized service. In later versions, we will gradually decentralize this part of the function, and deploy them to smart contracts, leaving only a small part of the core service.
HyperNode is the end node that processes RPC requests and sends responses to users through Gateway. HyperNode is usually run with the full node of the target blockchain (the RPC request targets). During the testnet phase #1, third-party operators were able to join and run HyperNodes.
Gateways collect and sort users’ requests, and route them to the proper HyperNode by the BlockPI Load Balancer. Gateway registration is expected to be open to third parties operators after HyperNode.
Validators are individual blockchain nodes monitoring each role in the network. It is the guarantee of the healthy operation of the network. With certain frequency and random algorithm, a Validator retrieves data from HyperNode and Gateway and writes to a block. With the consensus protocol, the data is verified and recorded by other Validators. In this way, the Validators become a blockchain network and supervise the other roles in the network.
Fisherman is another role responsible for the network security and can be considered as a special kind of user. It verifies that HyperNodes and Gateways are functioning properly in the same way as normal users sending requests.