[QoS][Cosmos SDK] Implement QoS for Cosmos SDK application layer
@commoddity is already working on this.
Since Jul 2, 2025.
Assessment
This issue has not been assessed yet.
Description
Objective
Implement a QoS package in the qos/cosmos folder that implements QoS checks and endpoint selection for the Cosmos SDK application layer.
Origin Document
The current QoS module for CometBFT covers only the consensus layer. The objective of this issue is to create a QoS layer that covers the Cosmos SDK application layer.
For example, endpoints like:
/cosmos/bank/v1beta1/balances/cosmos/staking/v1beta1/validators
Cosmos SDK API reference:
https://docs.cosmos.network/api
Goals
- Cosmos SDK endpoints (for example
pocket) are correctly checked using relevant quality checks and filtered out from the qualified endpoints pool if they fail them - Only good quality Cosmos SDK endpoints are selected from the available pool
- Any relevant documentation is updating
Deliverables
- Create a
qos/cosmospackage that utilizes the package structure defined inqos/evm(selected because it is the most developed of the existing QoS packages) to perform equivalent checks against Cosmos SDK endpoints - Any relevant documentation that explains the Cosmos SDK selection process is updated
-
pocketand other Cosmos SDK blockchains are updated in theconfig/service_qos_config.gofile
Non-goals / Non-deliverables
- Archival checks for Cosmos SDK endpoints are not included in this issue
General deliverables
- Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
- Testing: Add new tests (unit and/or E2E) to the test suite.
- Makefile: Add new targets to the Makefile to make the new functionality easier to use.
- Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.
Creator: @commoddity
Co-Owners: @adshmh @Olshansk
- 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 404 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 427 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oasdiff/oasdiff#1337 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dataiku/kiji-proxy#635 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hyperledger-firefly/signer#126 ·
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
jordansmall/spindrift#5748 ·
Maintainers usually reply within 1 day