Mark S. Lewis

> Offline signing seems like a significant feature or use case for the Fabric Gateway SDKs. I was unable to find it in the documentation anywhere except in the code...

I particularly like this change since the ioutil package has been deprecated since Go 1.16. 👍

@yacov are you thinking this change should only go into **main** and not the **release-2.5** branch? If that is the case, it seems like a wide-ranging change to unit test...

@johannww On ed25519 support for node fabric-gateway... I'm sure you already know the signing implementation is entirely pluggable. The client application can supply its own (ed25519) signing implementation and the...

I guess this refers to the development environment set up instructions in the [v2.2](https://github.com/hyperledger/fabric/blob/fb9551d2e5dcb8799c63a192c9cdf14a369e3053/docs/source/dev-setup/devenv.rst) and/or [v2.3](https://github.com/hyperledger/fabric/blob/a3a4d748d43cff29a9a25de67880999ffb9b7f98/docs/source/dev-setup/devenv.rst) documentation? I suspect that this commands were probably correct at the time of release,...

Confirmed that with current (v2.4) Fabric release and current fabric-samples, these things work: - Fabric install using install script. - Create test-network - Deploy Go chaincode - Run Go, Node...

Thank you for the issue report and investigation. Is it possible that you are hitting a failure in allocating threads used to deliver events because you have blocked processing of...

I don't think it is strictly necessary to create a new thread to deliver each block, although I guess the intent was to deal with event delivery asynchronously and not...

You are correct, there do look to be some issues here! > I think that there are two main problems here related to the documentation. It says that it signs...

You can get a block by transaction ID by evaluating the **GetBlockByTxID** transaction function on the **qscc** system chaincode. It takes two parameters: _channel name_ and _transaction ID_. The implementation...