You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, DRPCredentialStore handles private key storage. However, in cases involving a secp256k1 key, the networkNode also needs a matching private key. Managing these keys in multiple places can lead to inconsistencies.
Problem Description
Currently,
DRPCredentialStore
handles private key storage. However, in cases involving a secp256k1 key, thenetworkNode
also needs a matching private key. Managing these keys in multiple places can lead to inconsistencies.Proposed Solution
Add
packages/keychain
, and passsecp256k1PrivateKey
as a constructor parameter innetworkNode
. Same as libp2p: https://github.com/libp2p/js-libp2p/tree/main/packages/keychainImplementation PR
No response
Reference Issues
No response
Unresolved questions
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: