I have resolved this issue after making an update to writer, and changing the sub_policy to "Admins" instead of writers after making above change, i was able to make certificate update. once the admin

#kubernetes #fabric-ca-client #hyperledger-fabric #policies

Hi, I need to update/renew/rotate certificates for my HLF network (orderer and peer). so far using `peer channel update` command I have been able to update/renew/rotate 1. Admin certificate for ordere

#kubernetes #fabric-ca-client #hyperledger-fabric #policies

Hi Fabric Community, I'm exploring the offline transaction signing flow in hyperledger fabric by using Fabric Node SDK. I came across the following official tutorial. https://hyperledger.github.io/fab

#fabric #fabric-sdk-node #fabric-offline-tx-signing #hyperledger-fabric

You should NOT use a mix of LevelDB and CouchDB based peers on the same channel. Things may work at first, but if you later endorse data on a LevelDB peer that is not compatible with CouchDB, the tran

#network #hyperledger-fabric

I am not sure anyone tested mixed database types, have you tested it? Does it work? I'm not sure what happens to a LevelDB backed peer when it receives directions to build indices which only exist in

#network #hyperledger-fabric

Hi, community, I couldn't find any data regarding this, but is there a way or is it in the roadmap to have a hybrid discovery service? What I mean by hybrid is; having multiple peers on the same netwo

#network #hyperledger-fabric

Hi everyone, I'm currently designing a private blockchain network for a government Certification authority that has services for cloud-based digital signatures. in the network I designed, the governme

#hyperledger-fabric #privatedata #database #aws

Hello, I have a HLF running on azure AKS cluster. I have a couchdb acting as a wallet to store the identities of the blockchain admin and users. It is hosted along with all the other pods. when i crea

#couchdb #fabric-kubernetes #hyperledger-fabric #kubernetes #fabric-sdk-node

@Dave, Yes the NodeOUs are also configured. The logs state that the sub-policies are not being satisfied but there is evidently no such thing in the configtx.yaml which indicates/backs the claim. How

#fabric-kubernetes #hyperledger-fabric #chaincode

@Josh, I would love to see if fabric-operator and k8s-builder lifecycle make my life any easier. Need to find time to test them. Also, will keep my investigation of finding what went wrong with the fa

#fabric-kubernetes #hyperledger-fabric #chaincode

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

Argo provides an incredible workflow engine for Kubernetes. It is _more_ than enough to handle the workloads of running Fabric CLI binaries - you are on a solid course for workflow automation! Regardi

#fabric-kubernetes #hyperledger-fabric #chaincode

@Dave As you can see from the configtx.yaml that I've previously shared, all the orgs have LifecycleEndorsement policy set to Endorsement: Type: Signature Rule: "OR('Org1MSP.peer')" and from the examp

#fabric-kubernetes #hyperledger-fabric #chaincode

Arsh / Dave - a couple of questions: Arsh I don't recognize the yaml syntax where you are describing your network. Is this a descriptive format that you built in-house, or an input grammar supported b

#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

These are the logs from one of the peers of an org.

#fabric-kubernetes #hyperledger-fabric #chaincode

Thanks David, that was precisely what I was pondering over too but I would like to provide you a piece of information here. I'm using two channels and the network setup is as shown below. As per the s

#fabric-kubernetes #hyperledger-fabric #chaincode

Hi Josh, thank you for your quick response, I'd love to explore the new fabric-operator. However, I'm still intrigued as to what might have caused the error above mentioned. It is working fine in my d

#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

Hi Arsh, The `peer` CLI also uses some context and input parameters from the core.yaml configuration file - make sure that these are setting the correct MSP context when running the commit, or have su

#fabric-kubernetes #hyperledger-fabric #chaincode