Skip to content

Make settlement response caching configurable#39

Open
RobertClarke wants to merge 3 commits into
1.x.xfrom
prism-high-reject-analysis
Open

Make settlement response caching configurable#39
RobertClarke wants to merge 3 commits into
1.x.xfrom
prism-high-reject-analysis

Conversation

@RobertClarke

Copy link
Copy Markdown
Member

Summary

Adds independent cache controls for GET /public/v1/blocks/{hash}/settlement-artifacts while retaining its safe 5-second default TTL.
Repeated block-manifest traffic exposed a need for route-specific tuning, but the response also includes mutable fanout status and broadcast attempts, so it must remain short-lived by default.
Unset settlement controls inherit the global dynamic-cache TTL and stale-while-revalidate settings, preserving existing disable and shortening overrides.
Compose defaults, .env.example, API documentation, and regression tests are updated with the new settings and live-state constraint.

Validation

python3 -m unittest tests.test_prism_public_dashboard_api tests.test_prism_compose_profile tests.test_public_dashboard_api_contract (81 tests)

@RobertClarke
RobertClarke marked this pull request as ready for review July 16, 2026 23:33
@kiwidream
kiwidream changed the base branch from main to 1.x.x July 17, 2026 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant