Repository navigation
Drop Validation Cloud from the keyed cohort: every probe returns 401 - #3034
Merged
Merged
Conversation
The release would have published nine dead rows on public chain pages.
Validation Cloud is in the keyed cohort of all nine chain RPC specs and
has never produced a single measurement:
rpc_health 0 on all 27 (chain, region) series
rpc_call_total result="http_err" 22018
result="timeout" 5
successes 0
latency series none exist
The harness log names the cause, identically on every chain and region:
`http_err err=status 401`, plus `websocket: bad handshake` on the WS arm.
The key is invalid, expired, or was never provisioned. The probe runs at
full cadence, 19,437 calls in 24h, the same rate as QuickNode.
Removed from the nine chain specs: 18 provider blocks (warm and cold), 9
disclosure bullets, and 31 prose mentions. The prose matters as much as
the blocks: leaving "Alchemy, Chainstack, GetBlock, QuickNode, Dwellir
and Validation Cloud" in a subtitle would promise a provider the table
does not have. Each enumeration is rewritten rather than left dangling,
and no copy stated a cohort size, so no count goes stale.
Kept, deliberately:
rpc-cost Validation Cloud reads 167 and has been live in
production since #3012. It is a pricing bench, not a
probe, and the figure is real.
rpc-free-tier reads 1,219,510, a documented plan allocation.
Neither depends on the keyed endpoints, so neither is affected.
The Railway URLs are backed up to the secrets directory and removed from
the three keyed services, so we stop sending 19,400 authenticated-looking
requests a day to an endpoint that rejects every one of them. Restoring
is one command per variable once a working key arrives.
Gates: 253 specs valid, 597 tests pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release (#3021) would have published nine dead rows on public chain pages. Validation Cloud sits in the keyed cohort of all nine chain RPC specs and has never produced a single measurement.
The harness log names the cause, identically on every chain and every region:
The key is invalid, expired, or was never provisioned. The probe itself is healthy and running at full cadence: 19,437 calls in 24h, the same rate as QuickNode's 19,439.
What is removed: 18 provider blocks across the nine specs (warm and cold arms), 9 disclosure bullets, 31 prose mentions. The prose matters as much as the blocks. Leaving "Alchemy, Chainstack, GetBlock, QuickNode, Dwellir and Validation Cloud" in a subtitle would promise a provider the table no longer has, so each enumeration is rewritten rather than left dangling:
No copy stated a cohort size, so no count goes stale. Checked after the edit: zero remaining mentions in all nine files.
What is kept, deliberately:
rpc-costrpc-free-tierNeither depends on the keyed endpoints.
Infrastructure: the 54 Railway URL and WS variables are backed up to the secrets directory (600, outside the repo, verified absent from git) and removed from the three keyed services, so we stop sending 19,400 requests a day to an endpoint that rejects every one of them. Restoring is one command per variable the moment Validation Cloud supplies a key that authenticates.
Gates: 253 specs valid, 597 tests pass.