Hiero Block Node

Implementation of the Hiero Block Node, which is responsible for consuming the block streams, maintaining state and exposing additional targeted value adding APIs to the Hiero community.

Table of Contents

1. Project Links
2. Prerequisites
3. Overview of child modules
4. Getting Started
5. Contributing
6. Code of Conduct
7. License

Project Links

Prerequisites

• Java 21 (temurin recommended)
• Gradle (using the wrapper ./gradlew is highly recommended)
• Docker (recommended for running the projects)
• IntelliJ IDEA (recommended for development)

Overview of child modules

• server: implementation of the block node, which contains the main application and all the necessary code to run the block node.
• simulator: A simulator for the block node, which can be used to test the block node in a local environment.
• common: Module responsible for holding common literals, utilities and types used by the other modules.
• suites: A set of e2e tests that can be used to verify the correctness of the block node.
• tools: A set of command line tools for working with block stream files.

Getting Started

Refer to the Hiero Block Node Documentation Overview for more information about the project, design and guides.

Contributing

Whether you’re fixing bugs, enhancing features, or improving documentation, your contributions are important — let’s build something great together!

Please read our contributing guide to see how you can get involved.

Code of Conduct

Hiero uses the Linux Foundation Decentralised Trust Code of Conduct.

License

Apache License 2.0