CODEWITHSUNDEEP
blockchainhyperledgerhyperledger-fabric
detroitpro
detroitpro

Reputation: 3913

Why don't permissioned blockchains store their permissions in a blockchain?

In all the examples of 'permissioned' blockchains that I've found; they store the permissions in a centralized database.

Why wouldn't they store them on each node, in a decentralized blockchain of transactions that contain the current state of the permissions on the network?

Upvotes: 0

Views: 398

Answers (1)

yacovm
yacovm

Reputation: 5140

Since you tagged the question with hyperledger-fabric, I'll answer in that scope.

In Hyperledger Fabric - permissions are defined via membership of channels. More precisely - a channel corresponds to a blockchain, and the members of a channel are defined as organizations that are in the channel. Organizations in the channel are defined via MSP configurations, and the Fabric default MSP implementation uses x509 certificates to specify organizations, and members of organizations.

When a channel is created - these configurations (that define the permissions) are stored in the first block (genesis block) and later are updated via configuration blocks.

Upvotes: 5

Related Questions