Yes, think of ‘assets’ on the ledger as being ‘records’ in a database. Fabric uses a key/value model for storing individual ‘records’ in the state database. So in your example the record key may be “i

Hyperledger Fabric Contributor Meeting When: Every 4th Wednesday 9am US Eastern, 13:00 UTC Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Agendas and Recordings: https://wiki

No, that is not possible. The entire point of calling a function from one contract to another is to ensure they are committed atomically in a single transaction. If you want two different transactions

Not enough information here. What is the query? What is the exact error? Anything in CouchDB log? Can you reproduce when querying CouchDB directly? You say the queries now work, so is the problem repr

#fabric-sdk-java

I think we need to get one level deeper on a proposal… Any impact to ReadTheDocs? Can it transparently point to a different repo? How about the older release branches? How would maintainers be structu

I would certainly consider that. What is the full proposal? What has worked well for other projects? Could you start a new topic dedicated to the doc proposal? From: Ry Jones <rjones@...

I am not in favor of moving i18n translations to fabric core repo. There are assumptions that everything in fabric core repository should stay in sync and up to date including features, tests, and doc

PRs have started coming in for Fabric v3.0, e.g. removal of already deprecated features like Kafka ordering and system channel, as discussed in contributor meetings. So as to not impact the next v2.x

Hyperledger Fabric Contributor Meeting When: Every 4th Wednesday 9am US Eastern, 13:00 UTC Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Agendas and Recordings: https://wiki

Exactly what chaincode build steps are you doing? Are you following one of the samples or docs? What component is the suspected bug in? From: fabric@... <fabric@...

You can use either OrgMSP.member or OrgMSP.peer format, assuming you’ve configured the MSP for Node OU roles and provided the matching OU “peer” tag in the peer’s certificate. More details at https://

#fabric-kubernetes #hyperledger-fabric #chaincode

Here is the key lines: 2022-06-22 07:16:04.421 UTC [policies] func1 -> DEBU 777c66 Evaluation Failed: Only 0 policies were satisfied, but needed 3 of [ SchooleducationMSP/Endorsement HighereducationMS

#fabric-kubernetes #hyperledger-fabric #chaincode

Your LifecycleEndorsement is set to a majority of orgs. So you will need to approve the chaincode on at least 5 of 8 orgs and then send the commit request to at least those 5 orgs. It looks like your

#fabric-kubernetes #hyperledger-fabric #chaincode

The latest Fabric and Fabric CA fix releases are now available. Check out the release notes for details about fixes and improvements: https://github.com/hyperledger/fabric/releases/tag/v2.2.6 https://

Agenda topics for June 1 contributor meeting: Project update Performance Sandbox – Sam Yuan Etcd upgrade PR – Antoine Toulme From: David Enyeart <enyeart@...> Date: Tuesday, May 24, 2022 at 5:1

We’ve been cancelling several of the biweekly meetings, either due to schedules or no agenda topics. I’ve discussed with a few other maintainers and we’ve decided to shift to a meeting every 4 weeks l

Yes, applications built using the legacy SDKs continue to work against Fabric v2.4 and beyond. We encourage new projects to utilize the new Gateway SDKs as the legacy SDKs will likely become deprecate

I think you will struggle with a design that writes huge values to the ledger with frequent updates. Not just with the conflicts that you are seeing, but also with the growth of the blockchain. Can yo

Hyperledger Fabric Contributor Meeting When: Every other Wednesday 9am US Eastern, 13:00 UTC Where: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Agendas and Recordings: https://wi

Sorry to cancel Wednesday’s contributor meeting again, many of the regular participants are not able to attend this week. We’ll pick back up May 11th.