I am a beginner in hyperledger fabric and currently working on the 2.3 version. I deployed the chaincode and my database is CouchDB. I have created identities for the wallet but I am confused about how should peer of org 2 can interact with it. because only the admin is able to access, not other's identities.
How they will interact with each other?
can anyone please help me with it?
Related
I'm trying to connect api layer for go chaincode in hyperledger fabric but I didn't get any refrence for this. If anyone know anything about this please help me regarding this issue.
What type of documents i will need for apilayer node setup for go chaincode.
I am trying to move from Hyperledger composer to Fabric and I was looking at creating a similar pattern as composer to associate a participant to a connection identity.
Did you guys already tried to implemente a similar schema/pattern in fabric smart contract ?
Thanks a lot for you help.
Hello I am new to both HyperLedger Fabric and composer.I got confused with two terms. one is user in HyperLedger Fabric and another is participant in HyperLedger Composer.We have a set of users(including one administrator) in each organization along with peers in crypto-config.yaml file.
what is the roles and responsibilities of administrator user?
What is the roles and responsibilities of other users in crypto-config file?
It is said that a business network that is built using hyperledger composer can be deployed on hyperledger fabric network.What does business network contain and what does fabric network contain?
Difference between chaincode in fabric and transaction logic(which is written in javascript) in composer?
Admin credentials are used to create PeerAdmin card in composer which in turn is responsible for starting composer over fabric using your bna file and issue identity.
User is just extra set of credentials so that you will have some credentials initially to use the network. Later on you can issue new users using fabric CA.
Business network is nothing but a sort of abstraction over fabric using composer. Business network is deployed using bna file which has model file, transaction logic file, ACL file or query file. Fabric network is nothing but set of peers communicating with each other.
Chaincode is the smart contract which you directly deploy on fabric while the transaction logic used in composer is part of business network card which is deployed on fabric via composer. You cannot deploy standalone transaction logic on fabric, its deployed using composer with bna file, while chaincode you can deploy directly.
As far as I know, participant in hyperledger composer is identical to user in hyperledger fabric. However, in hyperledger fabric tutorials, they are mainly for testing mode. Thus, examples which you do are using cryptogen tool. This tool creates fix number of credentials based on "User" in your crypto-config.yaml. For instance, in the example about commercial paper 1, cryptogen creates 2 credentials for Admin and User1. Then, Isabella uses User1 credential (you can see in detail in code of addtoWallet.js). In the code, Isabella copies credential from User1 for making transaction.
Hyperledger composer looks like an abstraction running above Hyperledger fabric. It is more flexible when it allows to create credentials easily. When you create a participant and give them permission to access business network, you are generating credentials for them.
What are the differences between chaincode (in golang) and the bna file (created from hyperledger-composer)?.
And, how to add a peer into an existing hyperledger fabric network?.
This article can explain as a side-by-side (Golang and Composer model-driven approach) comparison -> https://blog.selman.org/2017/07/08/getting-started-with-blockchain-development/. The main difference is Hyperledger Composer is a set of abstractions, tools and APIs to model, build, integrate and deploy a blockchain solution (eg a business network for parties to transact on) to the blockchain network. Composer business network archives may be deployed to Hyperledger Fabric for execution.
As for your Fabric question - in order to add new peers to an existing organization you need to generate new certificates for your peers and sign them using the key of the root CA certs for the existing organizations. See this SO and links therein for more info -> Add Org or peer in Org dynamically in Hyperledger fabric
If we can build a business network in composer playground online(or) locally and then deploy network in fabric, make a REST call from an angular app (user facing) to connect to blockchain.
Do I still need to learn about the fabric implementation or its infrastructure, When composer has provided me with necessary toolings to work with blockchain.
What am I missing in this ?
ps:I am still in the early phase of learning hyperledger and so not very clear as to use which and when.
Composer just provide necessary tools to work with blockchain.
But if you want to build your own blockchain network, You need to learn about fabric.
In composer guide, it mainly showed two fabric networks: One organization Hyperledger Fabric and Two organizations Hyperledger Fabric.
Let's say if you want to add one more organization or add one more peer node for each organization. You can't implement the requirements just utilize composer.
I'm also quite new to this. So if I understand well your answer lissdy, if I follow the developer tutorial (https://hyperledger.github.io/composer/tutorials/developer-tutorial.html) my network will be deployed but with only one peer ? And I need to use fabric to go further ?