Base scheduled a mainnet RPC upgrade for April 21, creating a short chain-ops readiness check for apps using public RPC.
What Happened
Base scheduled a mainnet RPC endpoint upgrade for April 21 from 17:00 to 18:00 UTC, with minimal disruption expected but possible short request cancellations.
The item was selected in the coverage expansion pass because it has a concrete April 20 or next-24-hour decision value, a clear owner site, and source support strong enough for a short NewsArticle rather than a recycled headline.
Why It Matters
RPC changes affect dapp reliability, bots, indexers and users who rely on the public endpoint during the maintenance window.
Radar owns this because it is chain operations and dapp infrastructure discovery context. That owner fit matters because the same raw event can create very different user questions. The article is scoped to the question this site can answer without duplicating the same event across sibling properties.
What To Watch Next
Watch app status pages, fallback RPC routing and whether any user-facing transactions fail during the hour.
Readers should treat this as a decision-support update, not a permanent model change. If the next official report, exchange note, status update, or market board contradicts the current setup, the angle should be rebuilt from the new source rather than stretched from this snapshot.
Decision Context
The practical value of this update is the timing. It gives readers a defined checkpoint for today rather than a broad evergreen lesson: compare the official source with the current market, lineup, exchange or protocol board, then decide whether the information is already priced. If the board has moved too far, the right action can be to wait for the next official update instead of forcing a stale entry.
The source list was kept narrow on purpose. Official league, exchange, protocol or status-page material was preferred where available, with reputable market coverage used when the event is a reported funding, flow or security-context update. That keeps the article tied to a concrete delta rather than a loose headline.
Keep the next update cycle visible, because a confirmed lineup, settlement note, status change or follow-up filing can quickly turn this snapshot into a different decision.
Continue this cluster
Related notes in the april-20-chain-ops-board cluster:
This cluster starts here; related updates will be added as the board develops.
