Mark S. Lewis

A Makefile was added as part of PR #134.

I created a prototype implementation by: 1. Move all the Node client code that can be implemented without using Node standard packages into a `node/src/core` sub-directory. This required: 1. Implement...

My current thinking is that refactoring the current Node implementation so that it (or parts of it) can be run in a browser environment is impractical. It probably makes sense...

Intermittent failures are still occurring, such as: ``` java.util.NoSuchElementException: No value present at java.base/java.util.Optional.get(Optional.java:143) at org.hyperledger.fabric.client.CommonBlockEventsTest.sends_valid_request_with_specified_start_block_number(CommonBlockEventsTest.java:155) ``` and ``` java.util.NoSuchElementException: No value present at java.base/java.util.Optional.get(Optional.java:143) at org.hyperledger.fabric.client.CommonBlockEventsTest.sends_valid_request_with_specified_start_block_number_using_sign_bit_for_unsigned_64bit_value(CommonBlockEventsTest.java:175) ```

From my perspective, a new sample is not required. Just an update to the tutorial. The preferred approach to debug and do rapid development of smart contracts is to use...

Go bindings for the Fabric protobufs generated using the newer Go protobuf API are published as hyperledger/fabric-photos-apiv2. See docs for details: https://hyperledger.github.io/fabric-protos/ It is possible that referencing both versions of...

fabric-photos-go-apiv2 is just generated using the protoc compiler from the same protobuf definitions (in this repository) as fabric-protos-go. To generate different output would require different input. I think modifying the...

The fabric-protos-go package continues to use the deprecated protoc compiler and Go protocol buffer API precisely because of the incompatibilities you've hit. fabric-protos-go-apiv2 is the equivalent using the new protoc...

I agree that updating [fabric-chaincode-go](https://github.com/hyperledger/fabric-chaincode-go) (and also [fabric-contract-api-go](https://github.com/hyperledger/fabric-contract-api-go)) to use [fabric-protos-go-apiv2](https://github.com/hyperledger/fabric-protos-go-apiv2) would be a good approach. With the potential for mixing different protobuf bindings in the same project to cause...

There is now a [github.com/hyperledger/fabric-chaincode-go/v2](https://github.com/hyperledger/fabric-chaincode-go/tree/main/v2) and an accompanying [github.com/hyperledger/fabric-contract-api-go/v2](https://github.com/hyperledger/fabric-contract-api-go/releases/tag/v2.0.0) that both use [fabric-protos-go-apiv2](https://github.com/hyperledger/fabric-protos-go-apiv2), which in turn uses [google.golang.org/protobuf](https://pkg.go.dev/google.golang.org/protobuf?tab=overview). Smart contract implementors can choose whether they want to work with the...