Payments portal emissions ANTS page can fail to load due to public RPC rate limiting

[kc-zero-lab]

Problem

The emissions ANTS page in the payments portal currently appears to depend on a public RPC endpoint for fetching on-chain data. That endpoint can rate limit requests, which means the page may fail to load data for users even when the portal itself is healthy.

Impact

• Users may see missing/stale/empty emissions ANTS data.
• The failure is external and intermittent, so it can be hard to reproduce and easy to misdiagnose as a frontend bug.
• Public RPC shared limits are not reliable enough for a production user-facing payments view.

Proposed direction

Find and implement a more reliable RPC/data access strategy for the payments portal, for example one or more of:

• Use a dedicated/private RPC provider with appropriate quotas and API key management.
• Add server-side proxying/caching/batching so users do not directly fan out to public RPC.
• Add fallback RPC endpoints and retry/backoff behavior.
• Surface a clear degraded-state UI when data cannot be loaded because the upstream RPC is rate limited.
• Monitor/log RPC rate-limit failures so we can distinguish upstream throttling from app errors.

Acceptance criteria

• Emissions ANTS page no longer relies solely on a public rate-limited RPC path for critical data loading.
• Rate-limit responses are handled gracefully with retry/fallback/degraded UI rather than a silent empty/broken state.
• The chosen approach is documented in code/config so future payments portal work does not reintroduce public RPC dependency for critical reads.
• Basic verification covers the current emissions ANTS data loading flow.

Notes

Raised from product/ops concern: the payments portal emissions ANTS page might not load data because it is getting rate limited by public RPC.