From RChain-API created by crypto-coder : JoshOrndorff/RChain-API#26
Making a general suggestions that we include a convenience feature in the NPM package for managing aliased pub-priv keypairs in a file, that can be loaded and used to sign transactions. Functions would include things like:
Create new KeyPair: myNode.createKeyPair( alias, add_to_keystore=true );
Get Public Key by Alias: myNode.getPublicKey( alias );
Sign a transaction: myNode.signTransaction( alias, DeployData );
The current API provides the ability to dynamically generate a keypair and sign text.
We can use this internally, but if we want to reuse these generated keys, we will need a way to persist, and retrieve them later. Since this NPM package will be used for backend applications, there are some situations where reused keys will need to either be passed into the NPM package, or managed internally by the NPM package.
From RChain-API created by crypto-coder : JoshOrndorff/RChain-API#26
Making a general suggestions that we include a convenience feature in the NPM package for managing aliased pub-priv keypairs in a file, that can be loaded and used to sign transactions. Functions would include things like:
The current API provides the ability to dynamically generate a keypair and sign text.
We can use this internally, but if we want to reuse these generated keys, we will need a way to persist, and retrieve them later. Since this NPM package will be used for backend applications, there are some situations where reused keys will need to either be passed into the NPM package, or managed internally by the NPM package.
Do we have a preference?