qs meng <qsmeng@...>
In fabric 2.0 alpha, fabtoken is introduced. I have the following puzzles.
1. The issue transaction can be endorsed only by the prover peer. I want to know what is checked by commiter peers. For example, two client dapps issue two kinds of tokens with the same token name. How to avoid this ?
2. Fabtoken uses fabric msp to check if a client app can issue fabtokens. I think this would limit fabtoken's application. True users are not client apps, but persons who use the client app.