hyperledger

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

In torii routing we have a macro that produces endpoints with a specific number of data items.

This macro's usability can be greatly improved by refactoring it to be a procedural macro with more explicit (and readable) syntax.

The tails file location after publishing a credential definition is not considering the white spaces in revocation tags, which leads to fail in uploading tails file but publishes the credential definition on the ledger