Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Torswitch context not to overlap with normal for better privacy #5

Open
ujscale opened this issue Oct 4, 2023 · 1 comment
Open
Assignees

Comments

@ujscale
Copy link

ujscale commented Oct 4, 2023

Is your feature request related to a problem? Please describe.
When both normal switch and torswitch coexist, its possible that normal switch overtakes all the peers in the attestation topic leaving nothing for torswitch. That can cause attestation to fail when torswitch tries to send. The reason is that torswitch is using the same mechanism for findling subnets, discovery and peerpool that normal has.

Describe the solution you'd like
Separate all the discovery, peerpool, connection quues from those of normal switch.
Make tor discovery a bit more frequent than normal.

@ujscale ujscale self-assigned this Oct 4, 2023
@ujscale
Copy link
Author

ujscale commented Oct 4, 2023

#4 The pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant