diff options
| author | MacroFake <falke.marco@gmail.com> | 2022-04-27 18:59:40 +0200 |
|---|---|---|
| committer | MacroFake <falke.marco@gmail.com> | 2022-04-27 18:59:46 +0200 |
| commit | f0a834e2f10a0aa60c7cc76e9f3eb090168a32e5 (patch) | |
| tree | 1ac3b85b9a0416e46b64d3b0f04b15b1ce650280 /test/functional/interface_rpc.py | |
| parent | 132d5f8c2f2397a4600a42203f413dafdb6bcc37 (diff) | |
| parent | 2ff8f4dd81dc484fe38ddd9db63cc8fd30192245 (diff) | |
Merge bitcoin/bitcoin#18642: Use std::chrono for the time to rotate destination of addr messages + tests
2ff8f4dd81dc484fe38ddd9db63cc8fd30192245 Add tests for addr destination rotation (Gleb Naumenko)
77ccb7fce15e340080f14c7626cf3dc63fcdee88 Use std::chrono for salting when randomizing ADDR destination (Gleb Naumenko)
Pull request description:
We currently assign a destination peer for relaying particular addresses of nodes every 24 hours, and then rotate. This is done for rate-limiting (ultimately for privacy leak reduction I think?).
Before this change, 24 hours was defined as uint. I replaced it with std::chrono, which is mockable and type-safe.
Also added couple tests for this behavior.
ACKs for top commit:
jonatack:
ACK 2ff8f4dd81dc484fe38ddd9db63cc8fd30192245
Tree-SHA512: 16f703ef3ffee13ce3afa82ca7b4baa27308af18cd2eececdce5565badfb68656a2ad9c4594b73772e4bfa99b3fb15f8e4089c1cb4be98c0bae6730a9d2f8a25
Diffstat (limited to 'test/functional/interface_rpc.py')
0 files changed, 0 insertions, 0 deletions