@@ -111,7 +111,6 @@ See Smart-Contract_.
111
111
112
112
.. _Channel :
113
113
114
-
115
114
Channel
116
115
-------
117
116
@@ -175,7 +174,7 @@ A broader term overarching the entire transactional flow, which serves to genera
175
174
an agreement on the order and to confirm the correctness of the set of transactions
176
175
constituting a block.
177
176
178
- .. _ Consortium :
177
+ .. _ Consenter-Set :
179
178
180
179
Consenter set
181
180
-------------
@@ -185,7 +184,7 @@ in the consensus mechanism on a channel. If other ordering nodes exist on the
185
184
system channel, but are not a part of a channel, they are not part of that
186
185
channel's consenter set.
187
186
188
- .. _ Consenter-Set :
187
+ .. _ Consortium :
189
188
190
189
Consortium
191
190
----------
@@ -197,15 +196,28 @@ networks have a single consortium. At channel creation time, all organizations
197
196
added to the channel must be part of a consortium. However, an organization
198
197
that is not defined in a consortium may be added to an existing channel.
199
198
200
- .. _Consortium :
199
+ .. _Chaincode-definition :
200
+
201
+ Chaincode definition
202
+ --------------------
203
+
204
+ A chaincode definition is used by organizations to agree on the parameters of a
205
+ chaincode before it can be used on a channel. Each channel member that wants to
206
+ use the chaincode to endorse transactions or query the ledger needs to approve
207
+ a chaincode definition for their organization. Once enough channel members have
208
+ approved a chaincode definition to meet the Lifecycle Endorsement policy (which
209
+ is set to a majority of organizations in the channel by default), the chaincode
210
+ definition can be committed to the channel. After the definition is committed,
211
+ the first invoke of the chaincode (or, if requested, the execution of the Init
212
+ function) will start the chaincode on the channel.
213
+
214
+ .. _Current-State :
201
215
202
216
Current State
203
217
-------------
204
218
205
219
See World-State _.
206
220
207
- .. _Current-State :
208
-
209
221
.. _Dynamic-Membership :
210
222
211
223
Dynamic Membership
@@ -241,7 +253,16 @@ peers that are assigned to a specific chaincode application. Policies can be
241
253
curated based on the application and the desired level of resilience against
242
254
misbehavior (deliberate or not) by the endorsing peers. A transaction that is submitted
243
255
must satisfy the endorsement policy before being marked as valid by committing peers.
244
- A distinct endorsement policy for install and instantiate transactions is also required.
256
+
257
+ .. _FabToken :
258
+
259
+ FabToken
260
+ --------
261
+
262
+ FabToken is an Unspent Transaction Output (UTXO) based token management system
263
+ that allows users to issue, transfer, and redeem tokens on channels. FabToken
264
+ uses the membership services of Fabric to authenticate the identity of token
265
+ owners and manage their public and private keys.
245
266
246
267
.. _Follower :
247
268
@@ -283,12 +304,15 @@ issues PKI-based certificates to network member organizations and their users.
283
304
The CA issues one root certificate (rootCert) to each member and one enrollment
284
305
certificate (ECert) to each authorized user.
285
306
286
- .. _ Initialize :
307
+ .. _ Init :
287
308
288
- Initialize
289
- ----------
309
+ Init
310
+ ----
290
311
291
- A method to initialize a chaincode application.
312
+ A method to initialize a chaincode application. All chaincodes need to have an
313
+ an Init function. By default, this function is never executed. However you can
314
+ use the chaincode definition to request the execution of the Init function in
315
+ order to initialize the chaincode.
292
316
293
317
Install
294
318
-------
@@ -298,9 +322,12 @@ The process of placing a chaincode on a peer's file system.
298
322
Instantiate
299
323
-----------
300
324
301
- The process of starting and initializing a chaincode application on a specific channel.
302
- After instantiation, peers that have the chaincode installed can accept chaincode
303
- invocations.
325
+ The process of starting and initializing a chaincode application on a specific
326
+ channel. After instantiation, peers that have the chaincode installed can accept
327
+ chaincode invocations. This method was used in the previous version of the chaincode
328
+ lifecycle. For the current procedure used to start a chaincode on a channel in
329
+ the new Fabric chaincode lifecycle introduced as an Alpha feature in Fabric v2.0,
330
+ see Chaincode-definition _.
304
331
305
332
.. _Invoke :
306
333
@@ -523,7 +550,14 @@ Proposal
523
550
--------
524
551
525
552
A request for endorsement that is aimed at specific peers on a channel. Each
526
- proposal is either an instantiate or an invoke (read/write) request.
553
+ proposal is either an Init or an invoke (read/write) request.
554
+
555
+ .. _Prover-peer :
556
+
557
+ Prover peer
558
+ -----------
559
+
560
+ A trusted peer used by the FabToken client to assemble a token transaction.
527
561
528
562
.. _Query :
529
563
@@ -590,7 +624,7 @@ A smart contract is code -- invoked by a client application external to the
590
624
blockchain network -- that manages access and modifications to a set of
591
625
key-value pairs in the :ref: `World-State `. In Hyperledger Fabric, smart
592
626
contracts are referred to as chaincode. Smart contract chaincode is installed
593
- onto peer nodes and instantiated to one or more channels.
627
+ onto peer nodes and then defined and used on one or more channels.
594
628
595
629
.. _State-DB :
596
630
@@ -630,11 +664,13 @@ Transaction
630
664
631
665
A transaction, 'T'
632
666
633
- Invoke or instantiate results that are submitted for ordering, validation, and commit.
634
- Invokes are requests to read/write data from the ledger. Instantiate is a request to
635
- start and initialize a chaincode on a channel. Application clients gather invoke or
636
- instantiate responses from endorsing peers and package the results and endorsements
637
- into a transaction that is submitted for ordering, validation, and commit.
667
+ Transactions are created when a chaincode or FabToken client is used to read or
668
+ write to data from the ledger. If you are invoking a chaincode, application
669
+ clients gather the responses from endorsing peers and then package the results
670
+ and endorsements into a transaction that is submitted for ordering, validation,
671
+ and commit. If using FabToken to create a token transaction, the FabToken client
672
+ must use a prover peer to create a transaction that is submitted to the
673
+ ordering service and then validated by committing peers.
638
674
639
675
.. _World-State :
640
676
0 commit comments