1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
crateix!;
//-------------------------------------------[.cpp/bitcoin/src/addrman.h]
/**
| Stochastic address manager
|
| Design goals:
|
| - Keep the address tables in-memory, and
| asynchronously dump the entire table to
| peers.dat.
|
| - Make sure no (localized) attacker can fill
| the entire table with his nodes/addresses.
|
| To that end:
|
| Addresses are organized into buckets that can
| each store up to 64 entries.
|
| ---------------------------------------
| Addresses to which our node has not
| successfully connected go into 1024 "new"
| buckets.
|
| - Based on the address range (/16 for
| IPv4) of the source of information, or
| if an asmap is provided, the AS it
| belongs to (for IPv4/IPv6), 64 buckets
| are selected at random.
|
| - The actual bucket is chosen from one of
| these, based on the range in which the
| address itself is located.
|
| - The position in the bucket is chosen
| based on the full address.
|
| - One single address can occur in up to
| 8 different buckets to increase
| selection chances for addresses that are
| seen frequently. The chance for
| increasing this multiplicity decreases
| exponentially.
|
| - When adding a new address to an occupied
| position of a bucket, it will not
| replace the existing entry unless that
| address is also stored in another bucket
| or it doesn't meet one of several
| quality criteria (see IsTerrible for
| exact criteria).
|
| ---------------------------------------
| Addresses of nodes that are known to be
| accessible go into 256 "tried" buckets.
|
| - Each address range selects at random
| 8 of these buckets.
|
| - The actual bucket is chosen from one of
| these, based on the full address.
|
| - When adding a new good address to an
| occupied position of a bucket, a FEELER
| connection to the old address is
| attempted. The old entry is only
| replaced and moved back to the "new"
| buckets if this attempt was
| unsuccessful.
|
| ---------------------------------------
| Bucket selection is based on cryptographic
| hashing, using a randomly-generated 256-bit
| key, which should not be observable by
| adversaries.
|
| ---------------------------------------
| Several indexes are kept for high
| performance. Setting m_consistency_check_ratio
| with the -checkaddrman configuration option will
| introduce (expensive) consistency checks for
| the entire data structure.
*/
//-------------------------------------------[.cpp/bitcoin/src/addrman.cpp]