From 93968f461bb47b863018ceac53f330d4ee541236 Mon Sep 17 00:00:00 2001 From: 0xOZ <52073989+0x0OZ@users.noreply.github.com> Date: Sun, 28 Apr 2024 22:21:50 +0300 Subject: [PATCH] Update public/content/developers/docs/consensus-mechanisms/poa/index.md Co-authored-by: Paul Wackerow <54227730+wackerow@users.noreply.github.com> --- .../content/developers/docs/consensus-mechanisms/poa/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/content/developers/docs/consensus-mechanisms/poa/index.md b/public/content/developers/docs/consensus-mechanisms/poa/index.md index 889f047854d..2b5939e257f 100644 --- a/public/content/developers/docs/consensus-mechanisms/poa/index.md +++ b/public/content/developers/docs/consensus-mechanisms/poa/index.md @@ -16,7 +16,7 @@ Proof-of-authority is a modified version of **[proof-of-stake](/developers/docs/ Proof-of-authority requires trusting a set of authorized signers that are set in the [genesis block](/glossary/#genesis-block). In most current implementations, all authorized signers retain equal power and privileges when determining consensus of the chain. The idea behind reputation staking is every authorized validator is well-known to everyone through things like know your customer (KYC), or by having a well-known organization being the only validator—this way if a validator does anything wrong, their identity is known. -Proof-of-Authority has different implementations, but the standard Ethereum implementation is **clique**, which implements [EIP-225](https://eips.ethereum.org/EIPS/eip-225). Clique is developer-friendly and an easy-to-implement standard, supporting all client syncing types. Other implementations include [IBFT 2.0](https://besu.hyperledger.org/stable/private-networks/concepts/poa) and [Aura](https://openethereum.github.io/Chain-specification). +There are multiple implementations of PoA, but the standard Ethereum implementation is **clique**, which implements [EIP-225](https://eips.ethereum.org/EIPS/eip-225). Clique is developer-friendly and an easy-to-implement standard, supporting all client syncing types. Other implementations include [IBFT 2.0](https://besu.hyperledger.org/stable/private-networks/concepts/poa) and [Aura](https://openethereum.github.io/Chain-specification). ## How it works {#how-it-works}