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
Copy file name to clipboardExpand all lines: keystore/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,8 @@ Design principles:
4
4
to wrap via a network layer if needed.
5
5
- Storage abstract. Keystore interfaces can be implemented with memory, file, database, etc. for storage to be useable in a variety of
6
6
contexts. Use write through caching to maintain synchronization between in memory keys and stored keys.
7
-
- Only the Admin interface mutates the keystore, all other interfaces
8
-
are read only.
7
+
- Only the Admin interface mutates the keystore, all other interfaces are read only. Admin interface
8
+
is plural/batched to support atomic batched mutations.
9
9
- Client side key naming. Keystore itself doesn't impose certain key algorithims/curves be used for specific contexts, it just supports a the minimum viable set of algorithms/curves for chainlink wide use cases. Clients define a name for each key which represents
10
10
the context in which they wish to use it.
11
11
- Common serialization/encryption for all storage types. Protobuf serialization (compact, versioned) for key material and then key material encrypted before persistence with a passphase.
0 commit comments