Repository navigation
the race bullet quoted one reading of a jittery rate - #2817
Merged
Merged
Conversation
It said Solana scores 254 races an hour. Five consecutive 15-minute windows read 203, 25, 46, 37 and 186, so 254 was one sample of something that swings by a factor of eight. A race needs two feeds to report the same pool trade, which is a sparse coincidence, so the jitter is the quantity's nature rather than a fault. Replaced with the order of magnitude and the comparison that actually carries the claim: it is back to the rate it ran at before the token-scoped feeds arrived. Two numbers from the #2809 commit message and PR body are also wrong, and recorded here since they are not in published copy and cannot be edited there: "Mobula was first on 85 of the 109 pool trades it reported, about 78%" used the matched-only denominator, which omits ahead_of_reference. On the actual races the figure is 114 of 415, about 27.5%, which is what the page publishes and what the fix was always about: it was 0.08%. "~1,200 trades on the bench pool" came from the same mistake and was already corrected in #2812. The defect and the fix are unaffected: OKX took 5 firsts in 415 Solana races after the filter, against 75,151 an hour before it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Flotapponnier
added a commit
that referenced
this pull request
Oct 5, 2026
From #2817: the bullet quoted one reading (254 races an hour) of a rate that swings between 25 and 203 across consecutive windows. Now states the order of magnitude and the comparison that carries the claim. The worker clones dev at BUILD time, so the methodology reaches the page from here. pnpm validate: 235 specs valid. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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 bullet said Solana "scores 254" races an hour. Five consecutive 15-minute windows read 203, 25, 46, 37, 186, so 254 was one sample of something that swings by a factor of eight. A race needs two feeds to report the same pool trade, which is a sparse coincidence, so the jitter is the quantity's nature rather than a fault.
Replaced with the order of magnitude plus the comparison that actually carries the claim: it is back to the rate it ran at before the token-scoped feeds arrived.
Two numbers from #2809 that were wrong
Not in published copy, so recorded here rather than editable there:
ahead_of_reference. On the actual races it is 114 of 415, about 27.5% — which is what the page publishes, and what the fix was always about: it was 0.08%.The fix itself is unaffected
OKX took 5 firsts in 415 Solana races after the filter, against 75,151 an hour before it. Checked for over-correction too: the four pool-scoped feeds are unchanged (351 vs 360 samples/h, -2%) and hold 97% presence over 24h, so the filter is not starving the column.
What I am NOT claiming: the exact percentages. At 415 races across three regions (~138 each) serialized's 83% carries roughly ±7 points, and the share window is in-memory and refilling since the last redeploy. Directionally settled, not precise yet.
pnpm validate: 235 specs valid. The bullet went over the 500 character cap twice before fitting.🤖 Generated with Claude Code