This is not an issue with the submitting client credentials, it is an issue with the peer credentials not matching the org credentials in the channel config. You must approve on a peer of your own

Hi all, I am facing the same problem as Tong Li mentioned in the first email. After successful installation of CC package on peers, the documents and other samples, get approval with in their org

Transaction consensus and validity in Fabric is not the same thing as the consensus mechanism used to build a fault tolerant ordering service. Have a look at

The ordering services job is to assemble blocks from transactions and determine the final order of the transactions. It doesn't participate in the validation of the endorsed transactions. Once the

From what I know, the orderer is just assembling blocks from application transactions composed of the endorser responses to proposals. Then sending the blocks to committing peers. How is that a

Hi, I am using the example https://github.com/chainHero/heroes-service/ with fabric-sdk-go beta version. When I try to register a new user, registrar part have same issues. I can't register a

For the contributor meeting scheduled for tomorrow, we'll do a quick project update, but there are no deep dive topics scheduled yet. If you have a proposal or other topic you'd like to discuss,

Hi Marina, I would check the order log to see what the problems are. You can find some help with what to look for with this stack overflow post:

In v2.0 we are promoting this pattern of org-specific collections, where the per organization collections implicitly exist so that you don't have to define them at all. I agree with your thought - if

Thank you for your explanation. I now understand it clearly. But this would cost huge efforts to maintain private data collections in production environment if there are hundreds of private

Excellent, thanks! I should have piped up on this earlier when I saw the call for mass-closure of old issues. Brian On 2/3/20 10:18 PM, David Enyeart

To clarify, as Jason mentioned the Jira FAB-33 got caught up in a recent mass cleanup of stale issues that hadn't been touched in a long time. Any issue that was automatically closed in error can be

A regulator or auditor would be modeled as any other organization. Example: Channel includes four organizations: 'Org1', 'Org2', 'Org3', 'regulator'. Create Org1Collection that includes (Org1,

Hi All, The fabric doc said: “Fabric v2.0 also enables new patterns for working with and sharing private data, without the requirement of creating private data collections for all combinations

Part of the chaincode instantiation process is to compile the JAR, this isn't something you can hijack in 1.4.x without modifying the source code. Fabric v2.0 (which released last week) provides a

Hi, Every time when i initiate the chaincode , it take time to build the jar. To skip this process for multiple times and to learn the flow of hyperledger CC flow, i am customizing the image. Usually

You really should use a different status for deferred feature requests than "Closed", because "decided not to implement this ever" is a closer inference from "Closed" than "maybe

I've seen some similar confusion to this on Rocketchat as well. FAB-33 was closed along with hundreds of other items in an overall cleanup of JIRA. Its closure does not indicate any mothballing or

> because the actualdata is unknown to verifiers/endorsers Well but you can have the endorsementpolicy be satisfied by a set of members that they are all in the collectionpolicy. Furthermore you can

I apologize for restarting this old topic, someone sent me a private message so I think the least I can do is to make the problem clear