diff options
| author | Vasil Dimov <vd@FreeBSD.org> | 2021-01-11 17:25:40 +0100 |
|---|---|---|
| committer | Vasil Dimov <vd@FreeBSD.org> | 2021-06-21 15:27:03 +0200 |
| commit | dd4e957dcdfc971a4a971995ff2db9fb787d23c3 (patch) | |
| tree | f0942d6f7cad7ec5a43094d07337c71644112d6d /doc/files.md | |
| parent | d197977ae2076903ed12ab7616a7f93e88be02e1 (diff) | |
| download | bitcoin-dd4e957dcdfc971a4a971995ff2db9fb787d23c3.tar.xz | |
test: ensure banlist can be read from disk after restart
With `banlist.dat` (being written in addrv1 format) if we would try to
write a Tor v3 subnet, it would serialize as a dummy-all-0s IPv6
address and subsequently, when deserialized will not result in the same
subnet.
This problem does not exist with `banlist.json` where the data is saved
in textual, human-readable form.
Diffstat (limited to 'doc/files.md')
0 files changed, 0 insertions, 0 deletions