Just 14 days to go!Know more about the Speaker @ Genesis DevCon

Thank you for reaching out again Dave, In my case, for some unknown reason, I had 1 good world state and 3 bad world state. After updating fabric image on peers and resetting all peers, the world

Indeed, I think there's often confusion about network topology when it comes to "organizations". To be clear, there are 3 types of users, orgs that operate ordering nodes, orgs that operate peer nodes

Hello Brian, Thank you so much for your guidance. It helps, we will develop the architecture according to your inputs. -- Thank you Regards Alok Gupta +91-9646579412

The blog posts are the right place to start your exploration of the issues, but you can't go much further without testing it yourselves. You should be apprehensive about depending upon any blockchain

We haven't seen such a problem in Fabric system tests (e.g. there are tests that repeatedly crash peers and ensures that peer restart recovers in-flight data with correct data integrity). The

Hello Mark & Christopher, Thanks for your reply. I have gone through the blog but I am still apprehensive whether we would be able to support hundreds or thousands of organisations? We did TPS

Alok, We have seen throughput in high hundreds of TPS to low thousands of TPS in Oracle projects. The scalability and performance depend on many factors well explained in Chris’ blog posts.

Hi, Recently I got a strange behaviour in my network regarding ledger height, that was not consistent. I solved that issue but, after a bit more investigation, I found that some values in world state

From memory (I could be wrong): If you are using a single instance CA, ca-cert.pem is the root cert for both TLS and non-TLS certs issues by ca-server, including the

Hi, I attached the orderer logs. Thanks again, Balazs

hi Balazs, could you attach full orderer log so we could diagnose? or pls observe orderer log to see how long it took to elect a leader, some thing similar to "Raft leader changed: 0 -> x" thx - J

I am unable to debug my smart contract from vs code debugger. Here is my setup: peer node is started with CORE_CHAINCODE_MODE=dev fabric-chaincode-node is run with --peer-chaincodedev=true $ npm

In addition to CORE_PEER_GOSSIP_EXTERNALENDPOINT for exposing the peer endpoints to other orgs, make sure you understand how anchor peers are configured to bootstap the cross-org

Private keys are never sent anywhere. Only public keys are included with transactions. If you are using the fabric-ca-client or any of the SDKs, by default privates keys are created on the local file

Hello All, We hold our regulardocumentation workgroup call this week, both Eastern and Western hemispheres.All US and European clocks have now moved back to standard time from daylightsavings, so call

Hi Dave, You are right and thank you for sending the lines of the default behaviour. After some investigations, I think I'm missing CORE_PEER_GOSSIP_EXTERNALENDPOINT. I have

'peer node reset' should only be used if you suspect your peer's data is corrupted - it resets all channels to genesis block so that peer can re-pull/re-process blocks, but wouldn't change block

Hi I understand that HLF uses a client server CA and each member has its own CA. But txn approvals I have a question about securely storing and sending keys. Are there any guidelines for this?

Hi, I tried raft recently, and ran into this strange behavior: When I invoke peer channel create ..., I always get &{NOT_FOUND} first, then &{SERVICE_UNAVAILABLE} 4 or 5 times. After that, everything