Hedera Mirror Node
Last updated
Last updated
The Hedera Consensus Service (HCS) is a gRPC API endpoint on the mirror node to stream HCS messages. It offers the ability to subscribe to HCS topics and receive messages for the topic subscribed to. API docs for the mirror nodes can be found here:
The non-production public mainnet mirror node serves to help developers build their applications without having to run their own mirror node. For production-ready mainnet mirror nodes, please check out , , or . When building your Hedera client via , you can use setMirrorNetwork()
and enter the public mainnet mirror node endpoint. The gRPC API requires TLS. The following SDK versions support TLS:
Java: v2.0.6+
JavaScript: v2.0.23+
Go: v2.1.9+
Requests are throttled at 100 requests per second (rps). This may change in the future depending on performance or security considerations. At this time, no authentication is required.
The endpoints provided below allow developers to access the testnet mirror node, which contains testnet transaction data.
The endpoints provided below allow developers to access the previewnet mirror node, which contains previewnet transaction data.
REST API Preview Testnet Root Endpoint:
Hedera Mirror Nodes use databases to store the transaction and event data organized in a structure that mirrors the Hedera Network. Once the mirror node receives record files from Hedera Consensus nodes, the data is validated and loaded into the database.
Setting up a Hedera Mirror Node involves both hardware and software components. The requirements can be found .
No, Hedera does not charge for running a mirror node. However, there are costs associated with purchasing the hardware, internet connection, and potential cloud service fees. The hardware and software requirements can be found .
To provide feedback or log errors, please refer to the and submit an issue in the Hedera Docs .