What is a HIP?

HIP stands for Hiero Improvement Proposal. A HIP is intended to provide information or initiate engineering efforts to update functionality under Hiero governance. The HIP should be technically clear and concise, and as granular as possible.

HIPs are the primary mechanism for proposing new features, collecting community input, and documenting design decisions for the Hiero codebase.

HIP Types

1. Standards Track — New feature or implementation.
   • Core: Protocol, algorithm, networking.
   • Service: Service layer.
   • Mirror: Record retrieval.
   • Block Node: Pruned record retrieval.
   • Application: Ecosystem software.
2. Informational — Design issue or guidelines.
3. Process — Process change. Meta-HIPs are Process HIPs.

Process

See HIP-1 for the current HIP process.

Before Submitting

1. Evaluate your idea and how it benefits the Hiero community.
2. Check existing proposals for duplicates.
3. Discuss on LFDT Discord or Hedera Discord.
4. Ensure it's generally applicable.