The natural way of working with CoreStack is to use grpc as the underlying communication mechanism. This should be considered for this solution. Additionally there are tools for generating a rest api on top of a grpc api (see https://github.com/grpc-ecosystem/grpc-gateway).
_ Generate a key_*
API for simple key management to generate a new private key.
API should be able to import a private key
Low priority: API should be able to generate a new private key that is derived from a parent key and
a derivation path (cf: https://github.com/ethereum/EIPs/issues/84)
_ Support for multiple keys_*
Need to have more than a single identity being handled.
_ Sign a transaction (without submitting it to a server)_*
(without submitting it to a server) API that you provide an unsigned JSON transaction to, and get the
RLP signed transaction back.
Sign an arbritary payload.
API – pass in bytes get signature for the bytes back