# HyperGraph Introduction
**HyperGraph introduction**
HyperGraph is a high-performance data network that provides data indexing and query services for all high-performance public chains and their DApps. It is an important data service infrastructure in the era of high-performance blockchains.
\*Currently, it has served 30+ projects based on Heco, BSC, HSC and other public chains, including Mdex, Dodoex, etc.
\*HyperGraph has core technical advantages, far exceeding the indexing ability of similar products
\*The development team has an average technical level of more than 10 years and hundreds of millions of user architecture experience
**HyperGraph node**
In order to further meet the sudden increase in business volume and quickly carry and process huge amounts of data, HyperGraph makes the node network public, and external developers can access nodes according to rules, and jointly provide data indexing and query services for demanders and realize revenue sharing.
\*The income is truly rewarded directly to Token holders through the business
\* Decentralization of server node ownership
\*Maintain distributed management of nodes and servers
\
**The importance of HyperGraph nodes and their requirements**
The index node, together with the front-end deployment gateway and the back-end public chain RPC node, form the entire HyperGraph data network. The node is the core entity that performs user data storage and query, and is the core component of the entire data network that most directly bears business pressure. Participating in the node is equivalent to being a franchisee of the HyperGraph data network, and can share the data dividends in the era of high-performance blockchain, and at the same time assume the following responsibilities:
\*Maintain the importance and high reliability of Internet services (such as self-maintaining nodes, 7x24 hours response must be guaranteed)
\*Conscientiously maintain the HyperGraph brand and intellectual property rights, and cannot share nodes and technologies to third parties on their own
\*Fancy the long-term value of HyperGraph's business, and actively develop and treat projects and customers seriously
**Node startup time**
In late April 2021, the Heco node will prepare the DAO pool
Node registration will start in mid-May 2021
In mid-May 2021, the BSC node will prepare the DAO pool
The preparation and training related to the node will be started in late May
The first phase of the node list will be finalized in late May 2021
Node network deployment and testing will be carried out in early June 2021
In early June, start user service migration and open service
The node network will be fully online in mid-June 2021\
\
**Node startup process**
A. Node registration
B. Node selection (select public chain, select performance level, maintainable level)
C. Node preparation (technical team formation, server procurement, account allocation, program installation and documentation manuals)
D. Node mortgage (formally mortgage the node pool, miners participate in the mortgage to the node pool)
E. Product launch and service opening
**Node registration conditions**
Consistent with HyperGraph's goals and development philosophy, and the currency holdings start at 100,000 HGT
\*The currency holdings include HGT deposited in the node reserve pool and non-collateralized HGT on the BSC or Heco chain address
\*Holding less than 100,000 HGTs can also be mortgaged to the node to obtain income after the node is opened
\
**Node registration method**
Heco public chain and BSC public chain will simultaneously open node registration
Log in to HG.network to participate in registration
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://en.docs.hg.network/network/hypergraph-introduction.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.