title: Different instantiations for different peers for multiple endorsements in Hyperledger Fabric
body: <p>AS per Fabric documentation, peer endorsements for a specific chaincode is specified during chaincode instantiations.</p>
  <p>i.e 'peer chaincode instantiate' .... with endorsements specified with '-P '</p>
  <p>Now I can specify which peer to instantiate the chaincode with and the endorsement policy.
  Like for example if you take the first-network example in Hyperledger Fabric (<a href="https://medium.com/@kctheservant/understanding-first-network-example-in-hyperledger-fabric-part-1-c03391af798" rel="nofollow noreferrer">https://medium.com/@kctheservant/understanding-first-network-example-in-hyperledger-fabric-part-1-c03391af798</a>), chaincode instantiation is done for a specific peer (instantiateChaincode 0 2), which means that chaincode is instantiated for peer0 in org2.</p>
  <p>Now can I instantiate the same for different peers in the same first-network example (instantiateChaincode 1 2, instantiateChaincode 0 1, instantiateChaincode 1 1 ..) each with a different endorsement policy for the same chaincode installed on all the peers  ?</p>
  <p>**<strong>'peer chaincode instantiate [MSP for peer0.org1] -C [channel] -c [chaincode] -P [policy1]'</strong></p>
  <p><strong>'peer chaincode instantiate [MSP for peer1.org1] -C [channel] -c [chaincode] -P [policy2]'</strong>**
  .
  .
  .</p>
  <p>each instantiation of the same chaincode but with different endorsements for each</p>
  <p>Thanks</p>
  <p>Edit: The Hyperledger Fabric docs specify that instantiation of chaincode can be done only once and for one peer after installation. So is there a way to introduce endorsements for each peer or at a method level in Fabric as such ?</p>