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: src/peer-store/README.md
+8-5
Original file line number
Diff line number
Diff line change
@@ -52,9 +52,11 @@ A `peerId.toString()` identifier mapping to a `Address` object, which should hav
52
52
53
53
#### Key Book
54
54
55
-
The `keyBook` tracks the keys of the peers.
55
+
The `keyBook` tracks the publick keys of the peers by keeping their [`PeerId`][peer-id].
56
56
57
-
**Not Yet Implemented**
57
+
`Map<string, PeerId`
58
+
59
+
A `peerId.toString()` identifier mapping to a `PeerId` of the peer. This instance contains the peer public key.
58
60
59
61
#### Protocol Book
60
62
@@ -74,8 +76,9 @@ For the complete API documentation, you should check the [API.md](../../doc/API.
74
76
75
77
Access to its underlying books:
76
78
77
-
-`peerStore.protoBook.*`
78
79
-`peerStore.addressBook.*`
80
+
-`peerStore.keyBook.*`
81
+
-`peerStore.protoBook.*`
79
82
80
83
### Events
81
84
@@ -107,8 +110,6 @@ All the known peer protocols are stored with a key pattern as follows:
107
110
108
111
**KeyBook**
109
112
110
-
_NOT_YET_IMPLEMENTED_
111
-
112
113
All public keys are stored under the following pattern:
113
114
114
115
` /peers/keys/<b32 peer id no padding>`
@@ -127,3 +128,5 @@ Metadata is stored under the following key pattern:
127
128
- Further API methods will probably need to be added in the context of multiaddr validity and confidence.
128
129
- When improving libp2p configuration for specific runtimes, we should take into account the PeerStore recommended datastore.
129
130
- When improving libp2p configuration, we should think about a possible way of allowing the configuration of Bootstrap to be influenced by the persisted peers, as a way to decrease the load on Bootstrap nodes.
0 commit comments