tari-project / tari / 5517430158 / 1
62%
development: 62%

DEFAULT BRANCH: development
Ran
Files 703
Run time 8s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 76.002% (-0.02%) from 76.023%
5517430158.1

push

github

web-flow 
feat: peer sync limiter (#5445)

Description
---
This adds more criteria to the peers that get sent during a discovery,
and on connect. Nodes should only send non-banned peers, who have been
active within the week. They should send a max of 1000 peers per
request. More discovery can occur when connecting to those new peers.

Motivation and Context
---
This helps to prevent trustworthy nodes from sharing bad peers, or junk
data over the network. It limits an attack surface to a reach of 1,
where a bad actor may sync 1000 max junk records to direct connections,
but these connections would never propagate the junk peers forward as
they'll never see them online.

How Has This Been Tested?
---
Unit test added for the filtering of peers. Untested in network
enviornment

What process can a PR reviewer use to test or verify this change?
---

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->

70610 of 92906 relevant lines covered (76.0%)

202927.81 hits per line

Source Files on job 5517430158.1