distributed-ledger

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:
        

Currently there seem to be 3 options for testing Corda:

1. MockNetwork
2. Driver DSL
3. Manually start a network then run tests

The MockNetwork is useful for testing flows but it doesn't implement an RPC interface so you can't use it in your Spring REST API tests.

The Driver DSL has an RPC interface but all the work appears to have to be done in the dsl closure which means you can't get

We generate templates with the Template parent class; one could be added for generated records and variants as well. At the moment this would only include toValue (which is slightly different for each); the record one would become the parent of Template (see #13765).

Right now client/build.rs uses cargo to run cargo fmt. This approach can cause cargo recursion problem (cargo doesn't like to be invoked multiple times from it self) especially when using cargo lints. So we need to use rustfmt instead of cargo fmt.

To replace cargo build inside this script we need to do more work and that's gonna be in another issue