When using trustedpeer, flooding check should not be done. #786
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-09#786
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When using a trustedpeer, these checks shouldn't be done because if there are more than 200K objects active in the network then we won't get all of them.
3384869299/src/class_receiveDataThread.py (L407)
3384869299/src/class_receiveDataThread.py (L432)
Thanks to BM-2cTWtwwQvhcTMnEgT1bhWDYrC6VpF9Jxve for reporting.
Makes sense and looks like I can do that.
@Atheros1 If you want you can review it. I didn't test it extensively, I just check that trustedPeer is not broken.