Mark S. Lewis

If you are happy to work on it then yes, please do pick it up. You might want to refer to the existing private key and HSM signer implementations and...

@bugslayer-332 Please let me know if you want to share any early code as you progress on this, or if you want to discuss approaches. I am happy to help...

Sure, no hurry. I just wanted to make sure you were getting any support you might need. 😄

Unless other samples are demonstrating API usage not already covered by the asset-transfer samples, I vote we skip them. In fact, I think we'd be better actively removing the legacy...

Should this issue also include removing the samples included in this repository? Maintaining one set of samples seems like a better use of resources and less confusing for users. We...

Could we take advantage of the fact that the fabric-samples repository has branches for each release? Maybe we could update the top-level README to point people to the branch appropriate...

I'm not really sure what additional maintenance is required. We already have a **release-2.2** branch to be maintained. I'm not sure why removing samples from **main** increases the maintenance burden....

@HandOfGod94 The Fabric Gateway client API uses a simplified (and more abstract) mechanism for dealing with client identity and signing credentials, and doesn't include an equivalent to Wallets. If you...

@Sayalikukkar thank you very much for the interest, and apologies for not getting back to you more quickly. It would be great if you can contribute any of the missing...

I think the Makefile should define the set of tasks (targets) that you might reasonably want to run locally when doing development on this project. A good guide for candidate...