Hedera Mirror Node

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:

REST APIHedera Consensus Service gRPC API

Mainnet

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 Arkhia, Dragonglass, or Ledger Works. When building your Hedera client via SDK, 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.

Java

//You will need to upgrade to v2.0.6 or higher
Client client = Client.forMainnet();
client.setMirrorNetwork(Collections.singletonList("mainnet-public.mirrornode.hedera.com:443"))

JavaScript

Go

Mainnet Mirror Node Endpoint: mainnet-public.mirrornode.hedera.com:443 REST API Mainnet Root Endpoint: https://mainnet-public.mirrornode.hedera.com

Testnet

The endpoints provided below allow developers to access the testnet mirror node, which contains testnet transaction data.

HCS Testnet Mirror Node Endpoint: testnet.mirrornode.hedera.com:443

REST API Testnet Root Endpoint: https://testnet.mirrornode.hedera.com

Previewnet

The endpoints provided below allow developers to access the previewnet mirror node, which contains previewnet transaction data.

HCS Previewnet Mirror Node Endpoint: previewnet.mirrornode.hedera.com:443

REST API Preview Testnet Root Endpoint: https://previewnet.mirrornode.hedera.com

FAQ

How is data stored in a Hedera Mirror Node? Is it a specific type of database, or does it use a unique data structure?

Hedera Mirror Nodes use PostgreSQL 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.

How can I set up a Hedera Mirror Node? What are the hardware and software requirements?

Setting up a Hedera Mirror Node involves both hardware and software components. The requirements can be found here.

Are there costs associated with running a mirror node?

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 here.

How can I provide feedback or create an issue to log errors?

To provide feedback or log errors, please refer to the Contributing Guide and submit an issue in the Hedera Docs GitHub repository.