Skip to content

Commit 157b841

Browse files
committed
[FAB-4098], [FAB-5041], [FAB-9055] Glossary updates
Add/improve defs for consortium, organization, member, anchor peer and ledger Change-Id: Iba7cf2499840e672cb5af169ffe74e83bbd958a8 Signed-off-by: pama-ibm <pama@ibm.com> Signed-off-by: joe-alewine <Joe.Alewine@ibm.com>
1 parent f508c20 commit 157b841

File tree

1 file changed

+52
-10
lines changed

1 file changed

+52
-10
lines changed

docs/source/glossary.rst

+52-10
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
*Needs Review*
21

32
Glossary
43
===========================
@@ -13,11 +12,15 @@ read the entire thing in one sitting if you like; it's pretty enlightening!
1312
Anchor Peer
1413
-----------
1514

16-
A peer node on a channel that all other peers can discover and communicate with.
17-
Each Member_ on a channel has an anchor peer (or multiple anchor peers to prevent
18-
single point of failure), allowing for peers belonging to different Members to
19-
discover all existing peers on a channel.
20-
15+
Anchor peers are used to bootstrap gossip communication between peers from
16+
different organizations. Cross-organization gossip is scoped to channels. In
17+
order for cross-org gossip to work, peers from one org need to know at
18+
least the address of a peer from another organization in the channel.
19+
Each organization added to a channel should identify at least one of its
20+
peers as an anchor peer. The anchor peer address is stored in the
21+
configuration block of the channel. Each organization that has a peer
22+
should have at least one (there can be more than one) of its peers
23+
defined as an anchor peer.
2124

2225
.. _Block:
2326

@@ -100,6 +103,18 @@ A broader term overarching the entire transactional flow, which serves to genera
100103
an agreement on the order and to confirm the correctness of the set of transactions
101104
constituting a block.
102105

106+
.. Consortium
107+
108+
Consortium
109+
----------
110+
111+
A consortium is a collection of non-orderer organizations on the blockchain
112+
network. These are the organizations that form and join channels and that own
113+
peers. While a blockchain network can have multiple consortia, most blockchain
114+
networks have a single consortium. At channel creation time, all organizations
115+
added to the channel must be part of a consortium. However, an organization
116+
that is not defined in a consortium may be added to an existing channel.
117+
103118
.. _Current-State:
104119

105120
Current State
@@ -229,16 +244,28 @@ channel, who then distribute them to other peers within the same member cluster.
229244
Ledger
230245
------
231246

232-
A ledger is a channel's chain and current state data which is maintained by each
233-
peer on the channel.
247+
A ledger consists of two distinct, though related, parts -- a "blockchain" and
248+
the "state database", also known as "world state". Unlike other ledgers,
249+
blockchains are **immutable** -- that is, once a block has been added to the
250+
chain, it cannot be changed. In contrast, the "world state" is a database
251+
containing the current value of the set of key-value pairs that have been added,
252+
modified or deleted by the set of validated and committed transactions in the
253+
blockchain.
254+
255+
It's helpful to think of there being one **logical** ledger for each channel in
256+
the network. In reality, each peer in a channel maintains its own copy of the
257+
ledger -- which is kept consistent with every other peer's copy through a
258+
process called **consensus**. The term **Distributed Ledger Technology**
259+
(**DLT**) is often associated with this kind of ledger -- one that is logically
260+
singular, but has many identical copies distributed across a set of network
261+
nodes (peers and the ordering service).
234262

235263
.. _Member:
236264

237265
Member
238266
------
239267

240-
A legally separate entity that owns a unique root certificate for the network.
241-
Network components such as peer nodes and application clients will be linked to a member.
268+
See Organization_.
242269

243270
.. _MSP:
244271

@@ -277,6 +304,21 @@ designed to support pluggable implementations beyond the out-of-the-box SOLO and
277304
The ordering service is a common binding for the overall network; it contains the cryptographic
278305
identity material tied to each Member_.
279306

307+
.. _Organization:
308+
309+
Organization
310+
-----------------
311+
Also known as "members", organizations are invited to join the blockchain network
312+
by a blockchain service provider. An organization is joined to a network by adding its
313+
Membership Service Provider (MSP_) to the network. The MSP defines how other members of the
314+
network may verify that signatures (such as those over transactions) were generated by a valid
315+
identity, issued by that organization. The particular access rights of identities within an MSP
316+
are governed by policies which are are also agreed upon when the organization is joined to the
317+
network. An organization can be as large as a multi-national corporation or as small as an
318+
individual. The transaction endpoint of an organization is a Peer_. A collection of organizations
319+
form a Consortium_. While all of the organizations on a network are members, not every organization
320+
will be part of a consortium.
321+
280322
.. _Peer:
281323

282324
Peer

0 commit comments

Comments
 (0)