quorum-key-manager
quorum-key-manager copied to clipboard
Consensys
A universal Key & Account Management solution for blockchain applications.
In order to be backward compatible with Orchestrate key-manager we should implement one-time-keys
json-rpc protocol support multiple request at once by appending requests into body. The goal is to make the interceptor aware of this and handle it
This includes : - gathering info on existing load tests tooling and scope - understanding or defining tests envs - updating or improving tests - defining tests targets / conditions...
# Description - [ ] Support Tessera encryption use-cases and curve/methods - [ ] Support Privacy plugin - [ ] Support Rollup encryption scheme
### Summary / User Story Currently, AWS clients (keys and secrets) only allow authentication using a static credentials mechanism which consists in passing the client secret and client id. AWS...
Manifest file should be accessed easily by end-users, it is now embedded in a go template which makes it hard to read and handle
We should add logging on qkm startup - Current Version - Git Hash - dependencies config - TLS config - App state / health summary Motivation is due to this...
keys should be imported under a transportation ephemeral key 
In order to be consistent with the initialization of other Vault Clients, such as AKV and AWS, when a new Hashicorp client is initilialize the communication should be validate and...