The HyperGraph developer team provides the basic tools and products for network construction. And the web ecosystem has different roles based on the different players, five of which are described below.
A. Core developers
The core developers are responsible for the development and maintenance of the base software, guidance on node construction standards and suggestions for performance optimization. He is also responsible for coordinating HyperGraph community governance and building some public resources, which are provided free of charge to the community.
B. Index Nodes
The HyperGraph data network consists of a series of index nodes linked together. Index nodes pledge HyperGraph passes (HGT) to provide indexing and query services, with a minimum of 100K HGT passes pledged as index nodes. The revenue of an index node includes query fees and service indexing rewards. It can also share the rewards of the node reward pool. The index node pledge acts as a supervisory role for the node, which must index data correctly and provide service reliability. The node's HGT can come not only from the node operator, but also from the coin holder's pledge. Nodes select subgraph definitions to index data, and developers evaluate the quality of indexed nodes and select better quality nodes. Users can also specify which node will handle the queries and supply the fees.
C. Application developers
A developer is an individual or team that develops subgraphs and corresponding handlers based on requirements. The developer meets the data query requirements of the application, does certain development, submits the developed subgraph to the index node, completes the data indexing, queries and displays it on the user interface. In addition to deploying subgraphs by pledging HGT, developers can also pledge HGT to mark the quality of subgraphs to obtain indexing priority, and at the same time, developers also realize the evaluation of nodes and subgraphs based on their professional experience and using experience of ordinary users.
Miners refer to HGT holders, as the index node needs HGT pledge to open the node. Except for the initial 100K, other shares can be pledged by miners participating in pledging their HGT amount to the index node to increase the competitive advantage of the index node, and they can share the revenue of the index node
E. Data User
DApp projects or individuals can use HGT payments to query the data in the indexed network to fulfill their needs, or even to interface with APIs to develop specialized statistics and other display interfaces.
Various roles enter the HyperGraph network to contribute to the overall network construction based on different resource conditions, technical capabilities and share of coin holding. Each index node attracts users to use the node through its own stable service reliability, developer evaluation, plus there are different cost strategies, and the node formally enters the service network and starts indexing and providing query services may be based on these cases.
A. The application developer signals the index node by deploying a specific subgraph and the index node starts to work.
B. The historical query volume of a certain node or subgraph, etc., also predicts the future service demand.
C. the HGT collateral volume of a certain node also provides an important reference for the automatic selection of the network. A higher collateral volume implies greater importance and confidence in service delivery.
The following details expand on how the various roles are implemented
The indexing nodes need to have hardware resources and build corresponding software facilities to index the data and provide query services. The hardware can be different depending on the service volume. The following three scales are described separately
suitable for individual developers or small business teams to participate in the construction as a hobby career. Provide less than 100 sub-graphs index, or the amount of data per block in <10 transaction processing (counted by 5s for block out time) this amount, do not need to build their own blockchain RPC Archive nodes, but use the free RPC resources provided by the core developers, the recommended hardware configuration is as follows.
suitable for medium-sized application teams to use or medium-sized application teams to contribute their own nodes to participate in the construction, provide indexes with <500 subgraphs, or data volume within 100 transactions per block, and respond to 200-500 requests per second. Medium-sized nodes can build their own blockchain RPC nodes or use RPC resources provided by the core developers, but add additional HGT collateral for the RPC resources.
suitable for large teams, or professional partners to participate in node construction. It can store more than 1000 subgraph indexes, and provide more than 1000 query requests per second. Large nodes need to build their own RPC Archive nodes, and support the vertical cut of index nodes.
In addition to indexing nodes, splitting can be supported on top of software. The back-end software facilities can be supported for split deployment. Software, large nodes, need specific the following software build, compile and run, etc. environment, as well as the corresponding environment of the basic deployment and maintenance capabilities.
A. Linux operating system
B. Docker containers or Rust language compilation environment
C. Nodejs development compilation environment
D. Postgres database
F. HyperGraph node core program
G. HyperGraph index node program
The specific services and support needed for the actual process are implemented by the core developers with appropriate help, programs and scripts, etc.
Core developers are the initiating and maintaining members of the entire HyperGraph network, and are responsible for providing technical support and other services to network members, including the following links.
A. High-performance blockchain networks pose challenges to existing technical architectures, HyperGraph builds infrastructure based on open source software such as Graph Node to accommodate high-performance blockchain networks.
B. Responsible for developing interaction interfaces beyond the underlying services, and for the development of basic operating rules and service standards for the HyperGraph network.
C. Assist in solving specific to practical problems in node operation, including hardware and software configuration, selection, optimization, etc.
D. Organize community members, coordinate community governance, reward distribution and node evaluation, rewards and punishments, and other specific network health operation related matters.