Getting Help

Use the channels below to get support, report issues, and stay current with Block Node releases and community discussions.

---

Support channels

Escalate in tier order:

Tier	Channel	Use for
1 - Community	Hiero Discord	General questions, community discussion
1 - Issues	hiero-block-node GitHub Issues	Bug reports, doc improvements
2 - Hashgraph DevOps	Shared coordination channel (provided at handoff)	Installation support, upgrade coordination, incidents
3 - P0 escalation	On-call contact (provided at handoff)	Production outages requiring immediate response

Response timeframes for Tier 2 and 3 are governed by the Operating Agreement, Exhibit B §7c.

---

Community

• Hiero Block Streams Community Group - <BLOCK_STREAMS_COMMUNITY_URL> (obtain from Hashgraph DevOps at handoff)

• Hiero Discord - discord.gg/hiero

• GitHub Discussions - hiero-ledger/hiero-block-node

---

Reference documentation

Block Node operator docs

• Block Node Overview

• Block Node Hardware Specifications

• Network Ports and Protocols

• Block Node On-Chain Registration (HIP-1137)

• Configuration Reference

• Metrics Reference

• Operator FAQ

• Troubleshooting

• Resetting and Upgrading the Block Node

Deployment guides

• Deploy with Solo Provisioner

• Deploy on Bare Metal (Kubernetes)

• Solo Provisioner Quickstart

Integration guides

• Connecting a Mirror Node to a Block Node

• Configure Consensus Node Streaming

Specifications

• HIP-1081 - Block Node

• HIP-1056 - Block Streams

• HIP-1137 - Block Node Discovery

• HIP-1357 - Block Node Tier 1 Rewards

• HIP-1193 - Block Stream Cutover

• HIP-1200 - hinTS

• HIP-1424 - Block Merkle Hashing

• HIP-1427 - Record File Wrapping

---

Useful diagnostic commands

When opening a support ticket or community thread, include:

solo-provisioner version --output=json
helm -n block-node list
kubectl -n block-node get pods,sts,svc,events
kubectl -n block-node logs <pod> --tail=500
uname -a && uptime && free -h && df -h