Skip to content
Hedera Improvement Proposal
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

What is a HIP?

HIP stands for "Hedera Improvement Proposal". These improvement proposals can range from core protocol changes, to the applications, frameworks, and protocols built on top of the Hedera public network and used by the community. The HIP author is responsible for building consensus within the community and documenting dissenting opinions, as well as tracking their HIP through the process outlined below.

What is Hedera Hashgraph?

Hedera Hashgraph is the only public network built on top of Dr. Leemon Baird’s Hashgraph consensus algorithm. Hedera goes beyond blockchain to provide the fast, fair, and secure environment needed to enable enterprise adoption of distributed ledger technologies. You can learn more about Hedera by reading the Hedera whitepaper, and for a more detailed understanding of the Hashgraph Consensus Algorithm you can check out the hashgraph algorithm whitepaper.


The goal of HIPs is to have a place to propose new features, to collect community thoughts and input on a particular issue, and further to document all these subject matters in one place. It’s a great way to document these discussions and proposals here on GitHub, because any revisions made on these text files will be recorded.


There are four types of Hedera Improvement Proposals:

  • A Standard HIP - describes any changes that affect most or all clients using or running Hedera Hashgraph, this can be a change to the network protocol, transaction validity rules, proposed application standards/conventions, or any changes or addition that affects the interoperability of applications using Hedera Hashgraph. Standard HIPs can be broken down into the following categories:

    • Core: This type of proposal includes improvements to the core Hedera Hashgraph protocol and services (cryptocurrency, smart contracts, file service, and consensus service).

    • Interface: This type of proposal includes improvements around client API/RPC specifications and standards, and also certain language-level standards.

    • Economics: This type of proposal includes improvements to the Hedera fee structure, token distribution, proof-of-stake, and other areas relating to the economics of Hedera.

  • An HRC - This type of proposal is a Hedera “request for comment” - HIPs under this distinction require elaboration or commentary from the core Hedera team before recategorizing or moving forward with the proposal.

  • An Informational HIP - This type of proposal provides general guidelines or information to the Hedera Hashgraph community, but does not propose a new feature. Informational HIPs do not necessarily represent Hedera Hashgraph community consensus or recommendation, and so users are free to ignore Informational HIPs.

  • A Process HIP - This type of proposal includes any changes that affect the Hedera development process. Process HIPs are similar to Standard HIPs but modify tools and software beyond just the core Hedera Hashgraph protocol. Proposals of this category are typically more than simple recommendations, often requiring users to pay attention and make subsequent changes to additional software. Because of the impact in the Hedera development process, these proposals often require a community-based consensus. Examples include but are not limited to: developer guidelines, changes to an existing decision-making process, and changes to the tools or environment used in Hedera development.


Each HIP should only be one single key proposal and/or idea. The idea should be focused and only issue to one subject matter to be successful. A HIP must meet certain minimum criteria: it must be clear and have a complete description of the proposed enhancement, the enhancement must represent a net improvement, the proposed implementation, if applicable, must be solid and must not complicate the protocol unduly.

Before Submitting

  1. Evaluate your idea: consider why you’d like to request changes or improvements, and how it benefits the Hedera Hashgraph community.

  2. Thoroughly look through those proposals already submitted to ensure there are no duplicates.

  3. Ask the Hedera Hashgraph community first if your idea is original, or has already been through the HIP process.

  4. Reevaluate your proposal to ensure sure the idea is applicable to the entire community and not just to one particular author, application, project, or protocol.


An excellent place to discuss your proposal and get feedback is in the issues section of this repository, or on, a community forum dedicated to discussing hashgraph; there you can start formalizing the language around your HIP and ensuring it has broad community support.

If you're still here and think you can suggest an improvement, please go ahead and file an issue; we love contributions!


Parties involved in this process are often, but not always, you (the HIP author), the Hedera Hashgraph Community, the HIP editors, the Hedera Governing Council (HGC), and/or Hedera Hashgraph LLC.

The following is the process that a successful HIP will move along:

  1. Work in Progress (WIP)

  2. Draft

  3. Last Call

  4. Accepted by the community

Note: steps 5 & 6 only apply to Standard HIPs requiring core protocol changes, and therefore Governing Council approval.

  1. Proposed to the HGC

  2. Accepted by the HGC

  3. Final

Alternative statuses include:

  • Deferred: HIPs with this status has been put off to be discussed again at a later date.

  • Rejected: HIPs with this status are either: fundamentally broken, not accepted by the community, or not accepted by the HGC.

  • Superseded: HIPs with this status were previously at some stage of acceptance, but is no longer considered state-of-the-art.

The status change of each HIP is requested by the HIP author and it is to be reviewed by the HIP editors. To update the status, use a pull request. For convenience, always include a link for people to continue discussing your HIP or see the conversations that have already taken place.


These improvement proposals are intended to be the community voice for changes, but the implementation of Hedera Hashgraph is left to the engineers working at Hedera, and decisions regarding the platform and codebase strategy or future roadmap are ultimately made by the Hedera Governing Council. At some point, Hedera may have their own improvement made separately from this community managed repository, and may make changes not outlined in an HIP.

These proposals and discussions have no effect regarding private (permissioned) implementations of the Hashgraph consensus algorithm; additionally, this repository and it’s contents are run by the Hedera Hashgraph community, which means they do not necessarily reflect the views and opinions of Hedera Hashgraph LLC.

You can’t perform that action at this time.