yacovm
yacovm
I generally support this idea, and am in favor of it, but unfortunately adding support for ed25519 in a safe manner is more complex than just adding the code for...
Aside from my comment above, the PR is missing [integration tests](https://github.com/hyperledger/fabric/tree/main/integration) that generate ed25519 crypto material, and run a network and transact to ensure everything is good.
Ok i understand this is still work in progress. So please tag me once you feel this is ready. Take into account that it will take quite a while for...
Doesn't this require a capability? Otherwise how will old validation code that activates the old idemix be able to parse the new idemix signed transactions?
@Param-S @jiangyaoguo what is your opinion on this?
> What's the progress for this PR? @Param-S and @tock-ibm are looking at it, please standby :)
> What's the progress for this PR? I'm sorry, but we're just too busy to review it. We will get there eventually but unfortunately I cannot commit to a deadline.
But Fabric cannot dynamically update a TLS certificate anyway... there is no API for that.
I'm pretty sure the file is loaded only at startup... and not upon every TLS handshake.