Closed aral closed 5 years ago
See discussion.
To clarify, you can specify the secret key and other options when creating the initial hyperdb instance and they are used (it’s the hypercore created afterwards that you have no control over currently)
Closing this as you can pass the secret key in the options and what I ended up exploring in the PR mentioned above is actually not necessary for creating a seamless device/node authorisation process for multiwriter.
In hypercore, you can specify
secretKey
in theoptions
object passed to the constructor.This allows you to, for example, generate the keys from a Diceware passphrase.
In order to support the same use case, you should be able to do the same with hyperdb.