Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

IBFT available in v1.0 note added #667

Merged
merged 4 commits into from
Jan 29, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file removed docs/Configuring-Pantheon/IBFT.md
Empty file.
3 changes: 3 additions & 0 deletions docs/Consensus-Protocols/Comparing-PoA.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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
than the Ethash Proof of Work consensus protocol used on the Ethereum MainNet.

Expand Down
3 changes: 3 additions & 0 deletions docs/Consensus-Protocols/IBFT.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,9 @@ description: Pantheon IBFT 2.0 Proof-of-Authority (PoA) consensus protocol imple

# 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.

In IBFT 2.0 networks, transactions and blocks are validated by approved accounts, known as validators.
Expand Down
3 changes: 3 additions & 0 deletions docs/Consensus-Protocols/Overview-Consensus.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ Pantheon implements a number of consensus protocols:

* [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`:

```json tab="Ethash"
Expand Down
3 changes: 3 additions & 0 deletions docs/Reference/JSON-RPC-API-Methods.md
Original file line number Diff line number Diff line change
Expand Up @@ -1928,6 +1928,9 @@ None

## IBFT 2.0 Methods

!!! note
IBFT 2.0 is under development and will be available in v1.0.

### ibft_discardValidatorVote

Discards a proposal to [add or remove a validator](../Consensus-Protocols/IBFT.md#adding-and-removing-validators) with the specified address.
Expand Down
4 changes: 2 additions & 2 deletions docs/Reference/Using-JSON-RPC-API.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

!!!note
:construction: IBFT is not currently supported. Support for IBFT is in active development.
!!! note
IBFT 2.0 and Permissioning are under development and will be available in v1.0.

### Block Parameter

Expand Down