Skip to content
Switch branches/tags

Latest commit

* Sidecar Transaction Records

Signed-off-by: Stoyan Panayotov <>

* set correct hip number based on PR number
added link for discussions

Signed-off-by: Stoyan Panayotov <>

* Small formating changes
Changed some protobuf fields

Signed-off-by: Stoyan Panayotov <>

* protobuf messages updates

Signed-off-by: Stoyan Panayotov <>

* Update hip name to Record Stream V6

Signed-off-by: Stoyan Panayotov <>

* Added svg diagram for the record stream flow

Signed-off-by: Stoyan Panayotov <>

* Set HIP status to DRAFT

Signed-off-by: Stoyan Panayotov <>

* Added description of file names, block numbers, cryptographic proofs, record stream flow

Signed-off-by: Stoyan Panayotov <>

* Fix formatting

Signed-off-by: Stoyan Panayotov <>

* Add SemanticVersion to RecordStreamFile and SideCarFile
Add HashObject to be used for running hash objects

Signed-off-by: Stoyan Panayotov <>

* Rename sideCar to sidecar everywhere
fix protobuf positions for sidecarRecordFile

Signed-off-by: Stoyan Panayotov <>

* Add SidecarMetadata type
Add protobuf definitions for the signature file
Backwards compatibility and rejected ideas entries

Signed-off-by: Stoyan Panayotov <>

* Fix some typos

Signed-off-by: Stoyan Panayotov <>

* Remove block number from record file names

Signed-off-by: Stoyan Panayotov <>

* Change signature type to SHA_384_WITH_RSA

Signed-off-by: Stoyan Panayotov <>

* Formatting fix

Signed-off-by: Stoyan Panayotov <>

* Changes on protobuf definitions

Signed-off-by: Stoyan Panayotov <>

* Changes to protobuf definitions and descriptions

Signed-off-by: Stoyan Panayotov <>

* Remove restriction to group sidecar records in separate files by type of record

Signed-off-by: Stoyan Panayotov <>

* Add record stream file format version

Signed-off-by: Stoyan Panayotov <>

* change int fields to int32

Signed-off-by: Stoyan Panayotov <>

* Add contract bytecode sidecar record type
Edit the examples of files generated
Update prototuf fields

Signed-off-by: Stoyan Panayotov <>

Git stats


Failed to load latest commit information.
Latest commit message
Commit time

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.

You can see the list of all HIPs on the official HIPs site.

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.


See hip-1 for details on the HIP process.


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.

Local Jekyll Site

You can run a local version of the HIPs dashboard site:

jekyll serve --livereload

The site will be available on http://localhost:4000.

You can read more about Jekyll on its official website


An excellent place to discuss your proposal and get feedback is in the issues section of this repository, or on Hedera's Discord Server; there you can start formalizing the language around your HIP and ensuring it has broad community support.


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.