Glossary
Terms | Definition |
---|---|
API key | A simple encrypted string generated by users and verified by BlockPI Hub. It is a pass to use the BlockPI Network service. |
Auto-Scaling | Setting of the following automatic purchase strategy when the current RU packages are fully consumed. |
BlockPI Hub | BlockPI servers which manage the user system, node rating and authenticator system, and accounting system. |
BlockPI Node Balancer | An algorithm BlockPI developed that governs how Gateways dispatch requests to HyperNodes. |
BlockPI Testnet | A BlockPI Testnet is a network constructed for testing purposes. It consists of multiple instances such as Testnet #1, #2, and so on. Testnet #1 has completed in September 2022. Typically, a Testnet provides incentives and is open to third-party operators and users. |
Gateway | Distributed nodes which collect and sort users' requests, and route them to the proper HyperNodes. |
Node Client | End nodes that process RPC requests and send the response back to the users. |
Pay As You Go | An option in Auto-Scaling. Directly deduction of the wallet balance for extra RU use if the wallet balance is greater than $0 and the RU balance is 0. |
IPFS | A distributed system for storing and accessing files, websites, applications, and data. |
Public User | Unregistered users who use BlockPI public endpoints for free. |
Registered User | Users who registered are able to generate API keys and enjoy advanced services. |
Request Unit (RU) | The basic unit used to calculate the users' usage for sending RPC requests. |
RU Package | An RU package contains a certain amount of RUs. Different RU packages come with varying numbers of RUs and expiration dates. |
Last updated