From 3cdc350fbd687a10831f9ac71eca5786bd9c54fc Mon Sep 17 00:00:00 2001 From: Florent Tapponnier <160007691+Flotapponnier@users.noreply.github.com> Date: Wed, 29 Jul 2026 13:09:15 +0200 Subject: [PATCH] report: remove hardcoded September reference in What to Watch Next --- src/content/reports/rpc/2026-08-state-of-public-rpc.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx b/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx index 8b384567..342aca0b 100644 --- a/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx +++ b/src/content/reports/rpc/2026-08-state-of-public-rpc.mdx @@ -182,9 +182,9 @@ As of August 2026, PublicNode is the only provider in this cohort with near-100% ## What to Watch Next -This is the first edition of the OpenChainBench RPC Report. Starting with the September 2026 edition, each report will track month-over-month movement across three signals: success rate shifts, latency ranking changes, and incident counts per provider. Providers that degraded, chains where the competitive landscape shifted, and new entrants to the cohort will all appear in that section. +This is the first edition of the OpenChainBench RPC Report. Starting with the next edition, each report will track month-over-month movement across three signals: success rate shifts, latency ranking changes, and incident counts per provider. Providers that degraded, chains where the competitive landscape shifted, and new entrants to the cohort will all appear in that section. -The metrics most likely to move between now and September: success rates on Base and Arbitrum foundation endpoints (both chains are actively investing in RPC infrastructure), and the provider count on HyperEVM (currently thin). +The metrics most likely to move next: success rates on Base and Arbitrum foundation endpoints (both chains are actively investing in RPC infrastructure), and the provider count on HyperEVM (currently thin). If you want to be notified when the next edition publishes, follow [@OpenChainBench](https://x.com/OpenChainBench) or subscribe to the [RSS feed](/reports/rpc/rss.xml).