[Request] Blacklists and Preference Lists for servicer nodes
@fredteumer is already working on this.
Since Dec 19, 2024.
Assessment
This issue has not been assessed yet.
Description
Objective
Send a relay to nodes within a Preference List or that are not part of a Blacklist.
Origin Document
Blacklists might be necessary to allow gateways deployed in country X to avoid interacting with nodes in country Y due to legal stuff. Or any other type of discrimination that the Gateway user might desire.
Preference Lists can be used to force the relay to be sent to the first available node from an ordered list. This is useful when there is another process, or user preference, that wants to use PATH's ability keep track of sessions, available nodes and BASIC checks (like session sealed) but want to perform some exotic node selection mechanism.
Goals
- Add logic to prevent node for being selected (regardless QoS mechanism) based on a Blacklist parameter.
- Add logic to send a relay to the first node in a Preference List if it is available to the owned apps.
- Add a parameters to the relayer function to support these list to be dynamic and selected on a per-relay basis.
General Comments
The current PATH seems to be focused on providing full QoS to relays, from basic health-checks that are specific to POKT to advanced ones designed for specific blockchains. I think that it might be useful to allow users to use PATH as a solution to bare minimum POKT related stuff, like session handling, proof sealed events, POKT-specific error handling and let users experiment on the specifics of the services that they want to serve.
- Dominant language
- Go
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pokt-network/path
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pokt-network/path#509 ·
-
bug gateway
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pokt-network/path#477 ·
-
config documentation evm portal-db portal-ui qos
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pokt-network/path#475 · 1 comment ·
-
[RADIX][TRON][SUPPLIER] Suppliers should not have to append additional API paths in their RM configMay be free again @adshmh claimed this 383 days ago, and no pull request is open. Openqos
pokt-network/path#443 · 1 comment · 3 assignees ·
-
[PORTALDB][CONFIG] Surface sanctions settings and thresholds as configurables in both the Config files and Portal DBMay be free again @commoddity claimed this 406 days ago, and no pull request is open. Openconfig documentation portal-ui qos
pokt-network/path#409 · 1 assignee ·
All issues in pokt-network/path
Similar issues
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
priority/4/normal status/needs-triage type/bug/unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
authelia/authelia#13292 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
blinklabs-io/actions#138 ·
Maintainers usually reply within 1 day
-
[UI] AlbumDetails collapses multi-genre list to single primary genre on viewports < lg breakpointOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day