[QOS][RADIX] Implement Radix QoS Checks
@adshmh is already working on this.
Since Jul 28, 2025.
Assessment
This issue has not been assessed yet.
Description
Objective
Create custom QoS for Radix Core API to ensure 99%+ Success Rate
Origin Document
Grove's Radix Docs: https://docs.grove.city/radix-api/intro
Goals
- Ensure 99%+ Success Rate on Osmosis when used with PATH on Pocket Network Morse
- Ensure 99%+ Success Rate on Osmosis when used with PATH on Pocket Network Shannon
- Ensure all functionality described in the Grove docs is available matches success rates
Deliverables
- Dynamic Archival Checks for Radix service
- Marshalling and Unmarshalling checks on Radix Core API requests
- Path handling for radix requests: The end payload must be /radix/core/<path_user_wants>, handle filling in that path so that RMs can be configured consistently
- Some kind of check to ensure the chain is correct (a la the
chainCheckfor EVMs) - Penalties and timeouts for nodes serving errors.
Non-goals / Non-deliverables
- Additional 9s of success rate. This is a first pass to ensure the baseline.
- Support or QoS for other Radix APIs (namely, Gateway API)
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: @fredteumer
- 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 402 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 425 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
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
kubernetes-sigs/kueue#17385 ·
Maintainers usually reply within 1 day
-
Tablet Pods keep only one of several topology spread constraints that share a label selectorPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
planetscale/vitess-operator#858 ·
Maintainers usually reply within 2 days
-
Realtime: ASR EOU language tags leak into the LLM conversation (unintended reply-language switching)Possibly taken @nexxtmobile claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
content:edit documentation effort:high
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
cloudflare/cloudflare-docs#34428 ·
Maintainers usually reply within 1 day
-
generate: duplicate-skill warning ignores lint.allow_overrides when a local skill shadows a builtinOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day