@@ -264,6 +264,16 @@ that allows users to issue, transfer, and redeem tokens on channels. FabToken
264
264
uses the membership services of Fabric to authenticate the identity of token
265
265
owners and manage their public and private keys.
266
266
267
+ .. _FabToken :
268
+
269
+ FabToken
270
+ --------
271
+
272
+ FabToken is an Unspent Transaction Output (UTXO) based token management system
273
+ that allows users to issue, transfer, and redeem tokens on channels. FabToken
274
+ uses the membership services of Fabric to authenticate the identity of token
275
+ owners and manage their public and private keys.
276
+
267
277
.. _Follower :
268
278
269
279
Follower
@@ -325,8 +335,8 @@ Instantiate
325
335
The process of starting and initializing a chaincode application on a specific
326
336
channel. After instantiation, peers that have the chaincode installed can accept
327
337
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 in the v2.0 Alpha release ,
338
+ lifecycle. For the current procedure used to start a chaincode on a channel with
339
+ the new Fabric chaincode lifecycle introduced as part of the Fabric v2.0 Alpha,
330
340
see Chaincode-definition _.
331
341
332
342
.. _Invoke :
@@ -557,6 +567,14 @@ proposal is either an Init or an invoke (read/write) request.
557
567
Prover peer
558
568
-----------
559
569
570
+ A trusted peer used by the FabToken client to assemble a token transaction and
571
+ list the unspent tokens owned by a given authorized party.
572
+
573
+ .. _Prover-peer :
574
+
575
+ Prover peer
576
+ -----------
577
+
560
578
A trusted peer used by the FabToken client to assemble a token transaction.
561
579
562
580
.. _Query :
@@ -669,8 +687,8 @@ write to data from the ledger. If you are invoking a chaincode, application
669
687
clients gather the responses from endorsing peers and then package the results
670
688
and endorsements into a transaction that is submitted for ordering, validation,
671
689
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.
690
+ uses a prover peer to create a transaction that is submitted to the ordering
691
+ service and then validated by committing peers.
674
692
675
693
.. _World-State :
676
694
0 commit comments