Hashgraph nodes must be able to calculate the influence of other nodes during the virtual voting process and calculation of the median timestamp. In a permissioned deployment of hashgraph, that influence will depend on the total number of nodes, ie the size of the network, 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 issued 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
- Approximately how much would it cost to store all txs history without a mirror network? Is it realistically affordable for a startup?
- What companies are we working with for security audits, and will these be completed before OA?
- Will the codebase be open-review before open access?
- Why would I want to proxy-stake my hbars to a node?
- What is Open Access?
- Do nodes need to know the size of the network?
- What is the difference between accounts & wallets?
- Is Hedera post-quantum resistant?
- When will the mainnet be Open Access?
- How is Proxy Staking different from DPoS?