Skip to content

Commit

Permalink
Updated active validators count from 29 to 32 (#211)
Browse files Browse the repository at this point in the history
* updated mainnet active validators count from 29 to 32
* - updated validators count to 21 for bsc testnet
  - added additional info. of 21 cabinets and 11 candidates for bsc mainnet
* removed outdated dev-outlook-2022.md file and its corresponding references
  • Loading branch information
deepcrazy authored Oct 26, 2023
1 parent 946904b commit 484efb9
Show file tree
Hide file tree
Showing 15 changed files with 23 additions and 45 deletions.
2 changes: 1 addition & 1 deletion docs/BSC-FAQs-validator.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Slashing is a punitive function that is triggered by a validator ’s bad action

### What is the process of getting selected as a validator node on BSC?

On BNB Smart Chain (BSC) network, validators are responsible for securing the network by processing transactions and signing blocks. Validator nodes are incentivized in the form of transaction fees for their good behavior. Currently, there are 11 validators on the testnest and 50 validators on the mainnet. Validators are selected every 24 hours. Anyone can become a candidate for the validator. To become part of the selection process of validators, the nodes have to stake their BNB. Validators can self-delegate (self-bound) BNB to themselves and can also receive delegations from any other BNB holders. The minimum amount for self-delegation is **2000BNB**. Only the top 29 highest-stake nodes are chosen to be part of the validator set. Get more details [here](https://docs.bnbchain.org/docs/validator/overview.html).
On BNB Smart Chain (BSC) network, validators are responsible for securing the network by processing transactions and signing blocks. Validator nodes are incentivized in the form of transaction fees for their good behavior. Currently, there are 21 validators on the testnet and 55 validators on the mainnet. Validators are selected every 24 hours. Anyone can become a candidate for the validator. To become part of the selection process of validators, the nodes have to stake their BNB. Validators can self-delegate (self-bound) BNB to themselves and can also receive delegations from any other BNB holders. The minimum amount for self-delegation is **2000BNB**. Only the top 32 highest-stake nodes are chosen to be part of the validator set. Get more details [here](https://docs.bnbchain.org/docs/validator/overview.html).

### How is the bad or malicious behavior of the validator nodes controlled in the BSC?

Expand Down
2 changes: 1 addition & 1 deletion docs/BSC-FAQs.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ Please read this [guide](./wallet/withdraw-en.md)

## How does BNB Smart Chain work? What is the architecture and consensus used?

BNB Smart Chain relies on a system of 50 validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees.
BNB Smart Chain relies on a system of 55 validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees.

There will be fewer validators on BNB Smart Chain testnet.

Expand Down
3 changes: 0 additions & 3 deletions docs/BSCmainnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,3 @@ To get an overview of the BNB Smart Chain, refer [here](learn/intro.md). To lear

## How to Build on BSC
You can build deploy [smart contracts](remix-new.md), [NFTs](nft-metadata-standard.md), [BEP20 Tokens](BEP20.md), and [BEP20 Upgradable Contracts](proxy.md) on the BNB Smart Chain.

## BSC Outlook
To get an overview of what is the current state and the future developements that BNB Chain's team is working refer [here](dev-outlook-2022.md).
2 changes: 1 addition & 1 deletion docs/beaconchain/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ and node RPC interfaces.
| | BNB Beacon Chain | BNB Smart Chain |
| ----------------- | ------------- | -------------------------------------- |
| Consensus | DPoS | PoSA |
| No. of Validators | 11 | up to 50 |
| No. of Validators | 21 | up to 55 |
| Mean Block Time | <1s | ~5s |
| Programmability | BEPs | Support EVM-compatible smart contracts |
| Cross Chain |[BEP3](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP3.md) introduces *Hash Timer Locked Contract functions* and further [mechanism](https://community.binance.org/topic/1892) to handle inter-blockchain tokens peg. | BSC comes with efficient [native dual chain communication](../learn/cross-chain.md); Optimized for scaling high-performance dApps that require fast and smooth user experience. |
Expand Down
2 changes: 1 addition & 1 deletion docs/beaconchain/learn/bc-staking.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## PoSA Consensus of BNB Smart Chain

BNB Smart Chain is an innovative solution to bring programmability and interoperability to BNB Beacon Chain. BNB Smart Chain relies on a system of 50 validators with Proof of [Staked Authority (PoSA) consensus](../../beaconchain/learn/genesis.md) that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.
BNB Smart Chain is an innovative solution to bring programmability and interoperability to BNB Beacon Chain. BNB Smart Chain relies on a system of 55 validators with Proof of [Staked Authority (PoSA) consensus](../../beaconchain/learn/genesis.md) that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.

## Staking on BNB Beacon Chain

Expand Down
19 changes: 0 additions & 19 deletions docs/dev-outlook-2022.md

This file was deleted.

8 changes: 4 additions & 4 deletions docs/dev-outlook/decentralization.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,13 @@ sidebar_position: 2
## Candidate ValidatorSet
In order to decentralize the network further, more validators should be introduced. Besides increasing the anti-censorship, it always increases the robustness and availability of the network. BSC should survive even if more than half of the validator set were censored or taken down in a hostile way.

Meanwhile BSC has 29 active validators and many inactive validators. The inactive validators have no reward so the incentive for the runner to ensure the node quality and the delegation from the BNB holders are not enough.
Meanwhile BSC has 32 active validators and many inactive validators. The inactive validators have no reward so the incentive for the runner to ensure the node quality and the delegation from the BNB holders are not enough.

BSC will introduce more validators, e.g. another 20 inactive validators, into the validator set as backups, which will be called “Candidates”.
BSC will introduce more validators, e.g. another 23 inactive validators, into the validator set as backups, which will be called “Candidates”.

Candidates will produce blocks and charge gas fees in BSC mainnet, but in a much less chance than the official validator set of 29 elected. The unavailable candidates will be slashed as well though in a smaller size. A decent motivation is expected to be maintained so that the candidate validators are willing to ensure the quality and help secure BSC.
Candidates will produce blocks and charge gas fees in BSC mainnet, but in a much less chance than the official validator set of 32 elected. The unavailable candidates will be slashed as well though in a smaller size. A decent motivation is expected to be maintained so that the candidate validators are willing to ensure the quality and help secure BSC.

In an extreme case, if a majority of the active 29 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose a re-election of active validator set.
In an extreme case, if a majority of the active 32 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose a re-election of active validator set.

## Temporary Maintenance Mode for Validators
Due to the design of ‘Parlia’ consensus, the absence of the validator, even if it is due to scheduled maintenance, will cause instability and capacity of BSC due to the extra waiting time and chain reorganization.
Expand Down
2 changes: 1 addition & 1 deletion docs/learn/consensus.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ The consensus protocol of BSC fulfills the following goals:
5. It allows modern proof-of-stake blockchain network governance.

## Validator Quorum
In the genesis stage, a few trusted nodes will run as the initial Validator Set. After the blocking starts, anyone can compete to join as candidates to elect as a validator. The staking status decides the top 29 most staked nodes to be the next validator set, and such an election will repeat every 24 hours.
In the genesis stage, a few trusted nodes will run as the initial Validator Set. After the blocking starts, anyone can compete to join as candidates to elect as a validator. The staking status decides the top 32 most staked nodes to be the next validator set, and such an election will repeat every 24 hours.

BNB is the token used to stake for BSC.

Expand Down
8 changes: 4 additions & 4 deletions docs/learn/intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ hide_table_of_contents: false

# Introduction

BNB Smart Chain is an innovative solution to bring programmability and interoperability to BNB Beacon Chain. BNB Smart Chain relies on a system of 50 validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection, malicious vote detection and other slashing logic guarantee security, stability, and chain finality.
Other than the 29 active validators, BSC will introduce more validators, e.g. another 20 inactive validators, into the validator set as backups, which will be called "Candidates".
BNB Smart Chain is an innovative solution to bring programmability and interoperability to BNB Beacon Chain. BNB Smart Chain relies on a system of 55 validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection, malicious vote detection and other slashing logic guarantee security, stability, and chain finality.
Other than the 32 active validators, BSC will introduce more validators, e.g. another 23 inactive validators, into the validator set as backups, which will be called "Candidates".

Candidates will produce blocks and charge gas fees in BSC mainnet, but in a much less chance than the official validator set of 29 elected. The unavailable candidates will be slashed as well though in a smaller size. A decent motivation is expected to be maintained so that the candidate validators are willing to ensure the quality and help secure BSC.
Candidates will produce blocks and charge gas fees in BSC mainnet, but in a much less chance than the official validator set of 32 elected. The unavailable candidates will be slashed as well though in a smaller size. A decent motivation is expected to be maintained so that the candidate validators are willing to ensure the quality and help secure BSC.

In an extreme case, if a majority of the active 29 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose a re-election of the active validator set.
In an extreme case, if a majority of the active 32 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose a re-election of the active validator set.

The BNB Smart Chain also supports EVM-compatible smart contracts and protocols. Cross-chain transfer and other communication are possible due to native support of interoperability. The BNB Smart Chain will be:

Expand Down
2 changes: 1 addition & 1 deletion docs/migration/evm-chains/chain-comparison.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ Polygon utilizes the **Proof-of-Stake (PoS)** consensus algorithm, whereas BSC e

In the PoS consensus algorithm, validators are chosen based on a user's commitment to the network in terms of its stake, meaning that the higher the stake, higher the chances of getting selected as a validator. On the other hand, **PoSA** is a combination of the **PoS** and the **PoA (Proof of Authority)** consensus mechanisms.

Utilizing the PoSA consensus mechanism, BSC was initially launched with **21** validators. However, now BSC supports a set of **44** validators, with **26** of them being active. In future, BSC plans to increase the active validators to **41**, and about **80-100** validators in total. The top validator candidates with the most bonded stakes are chosen to be part of the subset of active validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality. Other than the **41 active validators**, BSC also has a set of inactive validators known as the **Candidates**. Even though the chances of getting elected are less, the Candidates upon selection can produce blocks and charge gas fees in the BSC mainnet. Similar to Active Validators, unavailable candidates are slashed but for a smaller amount. In an extreme case, if a majority of the active 41 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose re-election of the active validator set.
Utilizing the PoSA consensus mechanism, BSC was initially launched with **21** validators. However, now BSC supports a set of **55** validators, with **32** of them being active. In future, BSC plans to increase the active validators to **41**, and about **80-100** validators in total. The top validator candidates with the most bonded stakes are chosen to be part of the subset of active validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality. Other than the **41 active validators**, BSC also has a set of inactive validators known as the **Candidates**. Even though the chances of getting elected are less, the Candidates upon selection can produce blocks and charge gas fees in the BSC mainnet. Similar to Active Validators, unavailable candidates are slashed but for a smaller amount. In an extreme case, if a majority of the active 41 validators get attacked and offline, Candidate Validators can report to BNB Beacon Chain about the stale blocking, resume it and eventually propose re-election of the active validator set.

In contrast, Polygon uses the **Proof-of-Stake (PoS)** consensus mechanism on its _Plasma/POS commit chains_. For any user willing to participate in the consensus process, users are required to stake MATIC tokens on the staking smart contracts on Ethereum mainnet. This staking indicates a user's commitment to the process. A slashing mechanism (removal of staked funds) is also implemented to discourage stakers from submitting invalid blocks, illegally verifying blocks, or executing invalid transactions. Requiring validators to put funds at risk before they can participate in consensus helps maintain the integrity of the network.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ In this section, we discuss and compare the differences in the architecture and
- **EVM Compatibility:** BSC is designed to be completely EVM-compatible. Support for the EVM allows interoperability and portability between BSC and other EVM-compatible blockchains. Whereas, Solana is non-EVM compatible and is built on a tech stack that the team built from scratch, resulting in interoperability and portability issues.
- **Consensus Algorithm:** In terms of consensus algorithms, both BSC and Solana rely on PoS merged with other energy-efficient mechanisms. Both of the consensus mechanisms employed by either of the blockchains are to overcome Ethereum’s high gas fees and slower transactions.

- **BSC:** the BSC network uses a merger of delegated PoS and Proof-of-Authority (PoA) termed the Proof-of-Staked-Authority (PoSA). Utilizing the PoSA consensus mechanism, BSC was initially launched with 21 validators. However, now BSC supports 50 validators, of which 29 are active validators, with plans to increase it to 41 in the near future. The top validator candidates with the most bonded stakes are chosen to be part of the subset of active validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.
- **BSC:** the BSC network uses a merger of delegated PoS and Proof-of-Authority (PoA) termed the Proof-of-Staked-Authority (PoSA). Utilizing the PoSA consensus mechanism, BSC was initially launched with 21 validators. However, now BSC supports 55 validators, of which 32 are active validators, with plans to increase it to 41 in the near future. The top validator candidates with the most bonded stakes are chosen to be part of the subset of active validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.

- **Solana:** uses a combination of Proof-of-Stake (PoS) and Proof-of-History (PoH). Solana's PoS-based consensus mechanism termed Tower BFT leverages the network's PoH mechanism as a clock before consensus to reduce communication overhead and latency. PoH is a method of incorporating time itself into the blockchain.
Every time a validator votes on a particular fork, voting is restricted to a fixed period of hashes known as the “slot”. Currently, one slot aims to have a duration of approximately 400 milliseconds (ms), i.e., 0.4 seconds. In reality, the block size varies between 800ms up to 2 seconds. During the block creation time, the network has a potential rollback point, but every subsequent vote doubles the amount of time that the network would have to stall before it can unroll that vote. In short, secondary votes make it much harder to undo the transactions executed in a particular slot. Therefore, a block with several votes has a greater chance of remaining a part of the chain permanently.
Expand Down
4 changes: 2 additions & 2 deletions docs/parameters.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ sidebar_position: 2

### Max Validator Count

- **11** validators on Testnet
- **29** active validators on Mainnet
- **21** validators on Testnet
- **32** active validators on Mainnet

### Validator Candidate

Expand Down
Loading

0 comments on commit 484efb9

Please sign in to comment.