Hedera Hashgraph- Architecture


As we all know, a governing council & public hashgraph network (Hedera) has announced a new, next-generation distributed public ledger, the Hedera hashgraph platform which will develop lightning fast, secure, fair, globally distributed applications. This is my second post of the series regarding Hedera Hashgraph and in this post I will explain its architecture.

Internet Layer

As shown in above figure, Hashgraph’s nodes are all computers on the internet. They communicate with each other by TCP/IP connections secured by TLS encryption with transient keys for consummate forward mystery. Hubs are tended to by IP address and port, as opposed to by symbolic names, so attacks on the DNS framework won’t influence the system.

Hashgraph Consensus Layer

The hubs take exchanges from customers and offer them all through the system with a gossip protocol. At that point all hubs run the hashgraph consensus algorithm to achieve concurrence on an agreement timestamp for every exchange and its agreement arrange ever. Every hub at that point applies the impacts of the exchanges in agreement request to change its duplicate of the common state. Along these lines, all hubs keep up an indistinguishable agreement state (inside any given shard).

Above figure is displaying us the architecture of Hedera Hashgraph. It consists of three services layer. These three layers are cryptocurrency, file storage, and smart contracts.


Cryptocurrency is intended to be quick, which prompts low exchange charges, making microtransactions practical. When the Hedera stage is running at scale, any client will have the capacity to run a hub in the system and gain cryptographic money installments for doing as such. Any client can make a record by just making a key combine, with no name or address joined to it. Alternatively, arrangements are made to enable a client to connect hashes of personality authentications. These can originate from any third party endorsement authority or candidate authority that the client picks. This is planned to permit administrative consistence, for cryptographic money accounts that will be utilized as a part of a ward with Know Your Customer (KYC) or Anti-Money-Washing (AMC) laws.

File Storage

The file framework enables clients to store data, with consensus on exactly what is stored and what is not stored. Each hub in the shard stores similar records, so they won’t be lost in the event that one of the hubs crashes. Stored data must be erased by those that were given consent. Along these lines, the record framework can go about as a revocation service. For instance, in the future, a client may be issued a driver’s permit from the Department of Motor Vehicles(DMV), and both the client and the DMV carefully sign the exchange that puts a hash of it into the record. Both have the privilege to evacuate the hash of the permit. The client can pick to demonstrate to somebody that they have a legitimate permit, by giving that individual a duplicate of the permit record, so the individual can check whether the hash is still put away in the record. On the off chance that the DMV renounces the permit, it would likewise erase the hash, to demonstrate the world that the permit is no longer substantial. If client tries to store the hash once more, without a mark from the DMV,it will be apparent that the hash was saved just by the client without DMV collaboration, and would not be viewed as legitimate proof of the client’s entitlement to drive. Documents are really saved as Merkle trees, however Headgraph gives Java classes to enable engineers to control them.

Smart Contracts

The Hedera ledger can run smart contracts written in Solidity. There currently exist large libraries of Solidity smart contract code, which can be run unchanged on Hedera. These allow for distributed applications to be easily built on top of Hedera.

With hashgraph, we truly have all the characteristics of a winning technology that can close the gap between the re-emergence of cryptocurrency world.