标签：peers fabric 成员 v2.3 peer Hyperledger 节点 channel 通道

Channels

A Hyperledger Fabric channel is a private “subnet” of communication between two or more specific network members, for the purpose of conducting private and confidential transactions. A channel is defined by members (organizations), anchor peers per member, the shared ledger, chaincode application(s) and the ordering service node(s). Each transaction on the network is executed on a channel, where each party must be authenticated and authorized to transact on that channel. Each peer that joins a channel, has its own identity given by a membership services provider (MSP), which authenticates each peer to its channel peers and services.

Hyperledger Fabric通道（channel）是两个或多个特定网络成员之间进行通信的私有“子网”，目的是进行私有和机密交易。

通道组成：成员（组织），每个成员的锚节点，共享账本，链码应用程序和排序服务节点。

网络上的每个交易都在一个通道上执行，在该通道上必须对各方进行身份验证并被授权在该通道上进行交易。

加入通道的每个对等节点都有成员资格服务提供商（MSP）赋予的自己的身份，该身份验证服务提供商为其通道的对等节点和服务鉴定每个对等节点身份。

 

To create a new channel, the client SDK calls configuration system chaincode and references properties such as anchor peers, and members (organizations). This request creates a genesis block for the channel ledger, which stores configuration information about the channel policies, members and anchor peers. When adding a new member to an existing channel, either this genesis block, or if applicable, a more recent reconfiguration block, is shared with the new member.

要创建新通道，客户端SDK会调用配置系统链码并引用诸如锚节点，和成员（组织）之类的属性。

该请求为通道账本创建一个``创世''块，其中存储了有关通道策略，成员和锚节点的配置信息。

在将新成员添加到现有通道时，与新成员共享此创世块或（如果适用）一个较新的重新配置块。

 

Note

See the Channel Configuration (configtx) section for more details on the properties and proto structures of config transactions.

有关配置事务的属性和原型结构的更多详细信息，请参见``通道配置（configtx）''部分。

 

The election of a leading peer for each member on a channel determines which peer communicates with the ordering service on behalf of the member. If no leader is identified, an algorithm can be used to identify the leader. The consensus service orders transactions and delivers them, in a block, to each leading peer, which then distributes the block to its member peers, and across the channel, using the gossip protocol.

通道上每个成员的主节点（leading peer)的选择确定哪个对等节点代该成员与排序服务进行通信。

如果还没有主节点，那么一个算法可以用于标识出主节点。

共识服务对交易进行排序并将其以块的形式交付给每个主节点，然后主节点把区块分发给其成员节点，然后使用gossip协议穿过通道。

 

Although any one anchor peer can belong to multiple channels, and therefore maintain multiple ledgers, no ledger data can pass from one channel to another. This separation of ledgers, by channel, is defined and implemented by configuration chaincode, the identity membership service and the gossip data dissemination protocol. The dissemination of data, which includes information on transactions, ledger state and channel membership, is restricted to peers with verifiable membership on the channel. This isolation of peers and ledger data, by channel, allows network members that require private and confidential transactions to coexist with business competitors and other restricted members, on the same blockchain network.

尽管任何一个锚节点都可以属于多个通道，因此可以维护多个帐本，但是没有账本数据可以从一个通道传递到另一个通道。

账本的按通道划分是由配置链码，身份成员资格服务和gossip数据分发协议定义和实现的。

数据的分发（包括有关交易，账本状态和通道成员资格的信息）仅限于通道上具有可验证成员资格的对等节点。

通过通道对对等节点和账本数据的这种隔离，允许需要私有和机密交易的网络成员与业务竞争者和其他受限制成员在同一区块链网络上共存。

 

 

 

 

https://hyperledger-fabric.readthedocs.io/en/latest/channels.html

标签：peers,fabric,成员,v2.3,peer,Hyperledger,节点,channel,通道
来源： https://blog.51cto.com/u_15077160/2914445

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。