Skip to content

feat(filter): use protocol peer management #2046

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

Closed
danisharora099 opened this issue Jun 21, 2024 · 0 comments · Fixed by #2047
Closed

feat(filter): use protocol peer management #2046

danisharora099 opened this issue Jun 21, 2024 · 0 comments · Fixed by #2047

Comments

@danisharora099
Copy link
Collaborator

This is a feature request

Problem

We currently have limited control over the peers that are used for Filter.

Every time a new subscription is created, getPeers() is called, which fetches a new list of peers based on the current nodes that are connected.

This poses as a blocker to retrieve, and control, nodes and perform operations such as renewals.

Proposed Solutions

Use the logic implemented in #2044 for Filter

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

Successfully merging a pull request may close this issue.

1 participant