From 014572cd4ff8ef65c693224d1927eadb997b7ea9 Mon Sep 17 00:00:00 2001 From: Simon Dudley Date: Mon, 30 May 2022 17:07:37 +1000 Subject: [PATCH] IBFT has immediate finality (#232) Co-authored-by: Alexandra Tran <12214231+alexandratran@users.noreply.github.com> --- docs/concepts/consensus/comparing-poa.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/concepts/consensus/comparing-poa.md b/docs/concepts/consensus/comparing-poa.md index 83aa3002..93752aae 100644 --- a/docs/concepts/consensus/comparing-poa.md +++ b/docs/concepts/consensus/comparing-poa.md @@ -34,11 +34,11 @@ Properties to consider when comparing the PoA consensus protocols are: ### Immediate finality -QBFT and Raft have immediate finality. -When using QBFT and Raft there are no forks and all valid blocks get included in the main chain. +QBFT, IBFT, and Raft have immediate finality. +When using QBFT, IBFT, and Raft there are no forks and all valid blocks get included in the main chain. -IBFT and Clique do not have immediate finality. -Implementations using IBFT and Clique must be aware of forks and chain reorganizations occurring. +Clique doesn't have immediate finality. +Implementations using Clique must be aware of forks and chain reorganizations occurring. ### Minimum number of validators