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

The tight coupling between CLI and doc only exists because someone thought it was a good idea to make the build fail if the documentation isn't updated according to the output of some script. However,

I agree. I also always said that documentation shouldn't belong in the Fabric core repository in the first place.

Take a look at this paper: https://arxiv.org/abs/2107.06922 A Byzantine Fault-Tolerant Consensus Library for Hyperledger Fabric Hyperledger Fabric is an enterprise grade permissioned distributed ledge

#orderer #sbft #multi-leader-ordering-service

You can try to telnet to the host:port, either from outside or from within the container.

#fabric-orderer

It's a connection problem... you need to solve it on your own as it's your environment.

#fabric-orderer

Check the logs of the communication infrastructure, by enabling gRPC debug.

#fabric-orderer

You use erasure coding to avoid data duplication of data that is not used frequently, such as the blocks of the ledger. However, to fetch the data you'd need to reconstruct it from several servers. In

I am simply asking to understand if the peers can connect to the orderers to pull blocks, to understand whether the problem is only in the gateway or in all communications between the peer and the ord

#hyperledger-fabric #tls #fabric-sdk-go

Can you send transactions to the orderer from a client without the gateway? Do peers get blocks from the orderers?

#hyperledger-fabric #tls #fabric-sdk-go

On second thought, you said that code works? How come when you only add a single certificate and you have two in the chain?

#hyperledger-fabric #tls #fabric-sdk-go

you have an interediate CA but you use AddCert which receives a single certificate object (not a PEM but literally the x509 certificate). you need to add both root CA and intermediate CA. Easiest is t

#hyperledger-fabric #tls #fabric-sdk-go

Can't you just issue the certificate with the same public key but with SANs? You don't need to do the config update if the public key of the TLS certificate stays the same. You can just change the cer

#consensus #configtxgen #fabric-orderer

Maybe on the application channel, the orderer MSP has an OU configured and your identity you used to submit the transaction was issued by a CA with a different OU?

You need to add the anchor peer separately after the channel is created in a separate transaction.

I am aware of companies that use validation plugins to complement the built-in endorsement policy checks because they have an atypical adversary model. I also think that endorsement plugins are useful

You can play with it, but, it's not ready for production yet.

The system channel is just a means of ordering service nodes to synchronize about channel creation. This way, when you submit a channel creation transaction to the first ordering service node, the sec

https://github.com/hyperledger/fabric-rfcs/pull/42

maybe it doesn't see the other peer(s)? you can check it with https://hyperledger-fabric.readthedocs.io/en/latest/discovery-cli.html

#fabric-peer