IBFT available in v1.0 note added (#667)

Signed-off-by: Adrian Sutton <adrian.sutton@consensys.net>
pull/2/head
MadelineMurray 6 years ago committed by GitHub
parent 3249bbfbd3
commit 5333876eb9
  1. 0
      docs/Configuring-Pantheon/IBFT.md
  2. 3
      docs/Consensus-Protocols/Comparing-PoA.md
  3. 3
      docs/Consensus-Protocols/IBFT.md
  4. 3
      docs/Consensus-Protocols/Overview-Consensus.md
  5. 3
      docs/Reference/JSON-RPC-API-Methods.md
  6. 4
      docs/Reference/Using-JSON-RPC-API.md

@ -6,6 +6,9 @@ Pantheon implements the Clique and IBFT 2.0 Proof of Authority consensus protoco
consensus protocols are used when participants are known to each other and there is a level of trust between them. consensus protocols are used when participants are known to each other and there is a level of trust between them.
For example, in a permissioned consortium network. For example, in a permissioned consortium network.
!!! note
IBFT 2.0 is under development and will be available in v1.0.
Proof of Authority consensus protocols allow faster block times and have a much greater throughput of transactions Proof of Authority consensus protocols allow faster block times and have a much greater throughput of transactions
than the Ethash Proof of Work consensus protocol used on the Ethereum MainNet. than the Ethash Proof of Work consensus protocol used on the Ethereum MainNet.

@ -6,6 +6,9 @@ description: Pantheon IBFT 2.0 Proof-of-Authority (PoA) consensus protocol imple
# IBFT 2.0 # IBFT 2.0
!!! note
IBFT 2.0 is under development and will be available in v1.0.
Pantheon implements the IBFT 2.0 Proof-of-Authority (PoA) consensus protocol. IBFT 2.0 can be used for private networks. Pantheon implements the IBFT 2.0 Proof-of-Authority (PoA) consensus protocol. IBFT 2.0 can be used for private networks.
In IBFT 2.0 networks, transactions and blocks are validated by approved accounts, known as validators. In IBFT 2.0 networks, transactions and blocks are validated by approved accounts, known as validators.

@ -11,6 +11,9 @@ Pantheon implements a number of consensus protocols:
* [IBFT 2.0](IBFT.md) (Proof of Authority) * [IBFT 2.0](IBFT.md) (Proof of Authority)
!!! note
IBFT 2.0 is under development and will be available in v1.0.
The genesis file specifies the consensus protocol for a chain `config`: The genesis file specifies the consensus protocol for a chain `config`:
```json tab="Ethash" ```json tab="Ethash"

@ -1928,6 +1928,9 @@ None
## IBFT 2.0 Methods ## IBFT 2.0 Methods
!!! note
IBFT 2.0 is under development and will be available in v1.0.
### ibft_discardValidatorVote ### ibft_discardValidatorVote
Discards a proposal to [add or remove a validator](../Consensus-Protocols/IBFT.md#adding-and-removing-validators) with the specified address. Discards a proposal to [add or remove a validator](../Consensus-Protocols/IBFT.md#adding-and-removing-validators) with the specified address.

@ -76,8 +76,8 @@ The `ETH`, `NET`, `WEB3`, `CLIQUE`, and `IBFT` APIs are enabled by default.
Use the [`--rpc-api` option](Pantheon-CLI-Syntax.md#rpc-api) to enable the `ADMIN`, `DEBUG`, and `MINER` APIs. Use the [`--rpc-api` option](Pantheon-CLI-Syntax.md#rpc-api) to enable the `ADMIN`, `DEBUG`, and `MINER` APIs.
!!!note !!! note
:construction: IBFT is not currently supported. Support for IBFT is in active development. IBFT 2.0 and Permissioning are under development and will be available in v1.0.
### Block Parameter ### Block Parameter

Loading…
Cancel
Save