CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1137 Commits
44 Branches
214 Tags
190 MiB
 
 
Tag: Branch: Tree: cfd9a11847
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cfd9a11847'
${ noResults }
besu/docs/Permissions/Permissioning-Overview.md

1.4 KiB
Raw Blame History

description: Pantheon Permissioning feature

Permissioning

A permissioned network is a network where only specified nodes and accounts (participants) can participate. Nodes and accounts outside those specified are prevented from participating. Permissioned networks can have node permissioning enabled, account permissioning enabled, or both.

!!! note In peer-to-peer networks, node-level permissions can be used to enforce rules on nodes you control. With node-level permissions only, it is still possible a bad actor could violate network governance and act as a proxy to other nodes.

Node Permissioning

Account Permissioning

Local

Local permissioning are specified at the node level. Each node in the network has a permissions configuration file. Updates to local permissioning must be made to the configuration file for each node.

Onchain

Onchain permissioning is specified in a smart contract on the network. Specifying permissioning onchain enables all nodes to read and update permissioning in one location.

!!! note Onchain permissioning for nodes is under development and will be available in v1.1. Onchain permissioning for accounts will be available in a future Pantheon release.