Mark S. Lewis

@hyperledger/fabric-core-maintainers Now that Fabric v3 is the next scheduled release from the main branch codebase, what is the blocker to this PR being reviewed and merged? This submission has been...

> By the way, what about TLS? Have you tried spinning up a node with TLS certificates containing ed25519 keys? I am sure it should be possible as we don't...

@johannww likely because other changes have been merged in the meantime but this PR is showing as having merge conflicts that need to be resolved. You might need to rebase...

> I already solve this question on my mac m1. > > https://juejin.cn/post/7175001573045567548/ I'm not sure the arm64 Fabric Docker images you are using are a good solution for current...

@bh4rtp I _think_ you would need to either: 1. Set the key size and hash algorithm using the `crypto-keysize` and `crypto-hash-algo` config properties respectively; or 2. Explicitly create the CryptoSuite...

If you are passing explicit options to the HsmX509Provider, the `algorithm` option should be `EC`. A `hash` option should be `SHA3`. I think if the options are omitted then it...

It sounds like one end is not using the expected hash and, since when the client is using the default SHA-256 things seems to work, that suggests the issue might...

Since this package is now deprecated in favour of [`@hyperledger/fabric-gateway`](https://github.com/hyperledger/fabric-gateway), I do not plan to make any enhancements to function signatures / typing, particularly in the low-level APIs.

Just as some house-keeping, I am closing this issue as it has been inactive for a long time. Please comment if you want to resume work, although I would recommend...

A slight change to connection closing was deliver in the [v2.2.17 release](https://github.com/hyperledger/fabric-sdk-node/releases/tag/v2.2.17), which _might_ help with this issue. The workaround mentioned above does not seem ideal but the handling of...