Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove PKI backed QBFT docs #1685 #1687

Merged
merged 2 commits into from
Oct 1, 2024
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
13 changes: 0 additions & 13 deletions docs/private-networks/concepts/pki.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,17 +29,4 @@ When receiving connection requests, the incoming connection must be from another

[Configure TLS for the P2P communication using the Besu command line options](../how-to/configure/tls/p2p.md).

## Block proposal permissioning

:::caution

Only private networks using the [QBFT consensus protocol] support block proposal permissioning.

:::

Use certificates issued by a trusted authority to ensure only authorized validator nodes can propose new blocks in the network. The block hash is signed by the validator private certificate and included in the header of the proposed block as a [CMS (Cryptographic Message Syntax)]. This is used by other validators to verify that the proposer is authorized to create a block in the network.

[Configure block proposal permissioning using the Besu command line options](../how-to/configure/block-proposal-permissioning.md).

[QBFT consensus protocol]: ../how-to/configure/consensus/qbft.md
[CMS (Cryptographic Message Syntax)]: https://en.wikipedia.org/wiki/Cryptographic_Message_Syntax

This file was deleted.

Loading