Hashgraph nodes must be able to calculate the influence of other nodes during the virtual voting process and calculation of the median timestamp of transactions. In a permissioned deployment of hashgraph, that influence will depend on the total number of nodes, and so nodes will need to know that value. Of course, in a permissioned deployment, this is not an issue as new nodes will join only after a provisioning process - part of which would be updating the network on the new member and so larger network size. On the other hand, in Hedera's stake-weighted deployment of hashgraph, a node's influence is determined by the node's stake as a fraction of the total stake (which is the total number of hbars) and not the number of nodes. The first number in this calculation is readily available from the ledger, the second is the constant 50b. Consequently, in Hedera, the number of nodes is irrelevant to the consensus calculation.
Articles in this section
- How can I contribute to the OSS Hedera network services?
- What is the OSS license for Hedera network services?
- Will Hedera add additional services to the platform?
- Is Hedera censorship resistant?
- How does someone stand up a mirror node?
- What is a Hedera Improvement Proposal (HIP)?
- Where can I find the status of Hedera's mainnet and testnet?
- When was the genesis of the Hedera DLT, and what historical records are kept?
- Approximately how much would it cost to store all txs history without a mirror network? Is it realistically affordable for a startup?
- When will the codebase be available to review by the public?