[ENHANCEMENT][RELAY SIZE] Implement configurable relay data size limit on PATH
@commoddity is already working on this.
Since Jun 30, 2025.
Assessment
This issue has not been assessed yet.
Description
Objective
Users are always hungry for data but RPC calls are not always best serviced at humongous data sizes. We should implement a configurable data size limit on PATH with a reasonable default.
Origin Document
Goals
- Implement new environment variables with reasonable defaults
- Return an easy-to understand error when users exceed these limits
Deliverables
- Implement a new PATH environment variable
relay_request_size_limit(in bytes). Return HTTP413if the request exceeds this limit - Implement a new PATH environment variable
relay_response_size_limit(in bytes). Return HTTP413if the response exceeds this limit - Default both variables in
config/config.shannon_example.yamlto 10000000 (10MB)
Non-goals / Non-deliverables
- Any other environment variables
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
Co-Owners: @jorgecuesta
- Dominant language
- Go
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 381 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 404 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
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug P2 reliability
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
afreidah/s3-orchestrator#1564 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/gouroboros#2577 ·
Maintainers usually reply within 1 day
-
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 88/100
Maintainers usually reply within 1 day