Dave Kelsey
Dave Kelsey
Just target Fabric for now, or we could target the pingpong connector if one is ever written as the SUT is irrelevant
They should not have access to any publishing tokens, if they do it opens up the possibility of credentials being stolen and they do not need any publishing credentials. Note...
Need to patch the version in the shrinkwrap files to make sure they exist. Plus updated the devcontainer to ensure npm is at the latest so it can be used...
Ensure it is a cloned copy so the workload can't make dynamic changes, This would be useful for the workload so that it knows of 1. The identities available 2....
``` npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce...
Seems this is a recommendation for security hardening
fabric put's it in their readme at the top ``` [](https://scorecard.dev/viewer/?uri=github.com/hyperledger/fabric) ``` should be able to replace hyperledger/fabric with hyperledger-caliper/caliper but you can't as it's not configured correctly hyperledger/caliper...
This should be removed and is easy to do now that the ethereum connector has gone.
Currently a transaction submitted by a workload uses the first Peer listed in the network configuration for the MSP of the identity used. It should be possible for a workload...