Dave Kelsey

Currrently fixed-asset-base isn't tested by the build as the benchmarks specify a chaincode of fixed-asset which could test fixed-asset or fixed-asset-base. The way to solve this would be to upgrade...

For example ``` 2022.07.01-11:14:58.460 error [caliper] [connectors/v2/FabricGateway] Failed to perform query transaction [paginatedRichQuery] using arguments [{"selector":{"docType":"fixed-asset","creator":"client_nomatch","byteSize":1000}},2], with error: Error: Incorrect number of params. Expected 3, received 2 at RoundRobinQueryHandler.evaluate (/home/runner/work/caliper-benchmarks/caliper-benchmarks/node_modules/fabric-network/lib/impl/query/roundrobinqueryhandler.js:60:57)...

see https://github.com/hyperledger/caliper/1373 We can look at the same

Java chaincode has been failing to build (maven issues probably), also the dependencies specified in gradle are different between the 2 java chaincodes. I am not a fan of Java...

Fisco-bcos benchmarks fail to work due to incorrect benchmark format

1

To run the benchmarks there are 2 commands - npx caliper launch manager --caliper-workspace ./ --caliper-networkconfig ./networks/fisco-bcos/4nodes1group/fisco-bcos.json --caliper-benchconfig ./benchmarks/samples/fisco-bcos/helloworld/config.yaml - npx caliper launch manager --caliper-workspace ./ --caliper-networkconfig ./networks/fisco-bcos/4nodes1group/fisco-bcos.json --caliper-benchconfig ./benchmarks/samples/fisco-bcos/transfer/config.yaml...

Guaranteed JSON serialisation and deserialisation for java and javascript chaincodes

1

In fabric it's important that when serializing an object to a string that it results an a byte exact stream when run on different peers as part of the endorsement...

Currently we provide a network configuration for test-network and instructions on how to use, what would be good would be to extend this to other sample fabric deployments - [...

Update module dependencies for fabric Go Chaincode

3

- [ ] fabcar - [ ] fixed-asset - [ ] fixed-asset-base

when running the fisco-bcos benchmarks the repo reports loads of deleted, added or changed files. It seems that we might have files in the repo that aren't needed as well...