Repository navigation
fix(home): count tokens, not prediction rows; drop dead banned copy; honest Pro/Dev and health lines - #35
Merged
Conversation
…honest Pro/Dev and health lines - Home counter and KPI cell use unique_mints_predicted from /v1/stats when the api serves it (solsentry #396), with the row count as the fallback: 'over N tokens with outcome-tracked predictions, each auditable per mint'. - Remove the unused SenaTeaser component and its copy (a per-operator 'confirmed rugs, each verified on-chain' sample) and the unused 'Operators tracked' label. - 'Full history, graphs and alerts live in Pro / Dev' -> 'are coming'. - About: /health returns service status only; drop 'invariants checked daily'.
'open-source Haradrim patterns' (EN and PT acknowledgments) described Helius's public patterns we credit, not SolSentry, but read like the banned open-source claim. Reworded to 'public Haradrim patterns'.
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.
Why
Brief n, item 8 (solsentry BACKLOG §N).
/v1/stats.total_predictions, which counts prediction rows. Prod holds 213,506 rows over 114,168 tokens (01/10). solsentry#396 addsunique_mints_predicted(one count per token).src/lib/i18n-landing.tskept banned copy that would come back if a component reused it./healthreturns only{service, status}(read 01/10).What
NetworkStatsgains optionalunique_mints_predicted/unique_mints_resolved. When the api serves them, the home footer reads "LIVE • over N tokens with outcome-tracked predictions, each auditable per mint" (PT: "mais de N tokens com predição rastreada até o desfecho, cada uma auditável por mint"), and the KPI cell becomes "Tokens · outcome-tracked". Fallback: while the field is absent (api before #396), both keep today's row-based text. This is safe to merge before or after the api deploy.SenaTeasercomponent was imported nowhere. It is deleted, with allsena*keys and their per-operator sample ("This deployer has confirmed rugs on record, each one verified on-chain", LOCK-03). The unusedstatsLabelOperators("Operators tracked") is removed. The "fixed precision" line the BACKLOG cited was already gone (no%figure left in the file).easyProDev: "…live in Pro / Dev" → "…are coming in Pro / Dev" (PT: "chegam em breve no Pro / Dev").Checks
tsc --noEmitclean;eslintclean on the touched files.prettier --check:i18n-landing.tswas formatted.AboutClient.tsx,LandingClient.tsxandapi.tswere already non-compliant onmain(checked on theorigin/maincopies) and are left as they were, to keep the diff reviewable.ops/tools/check_landmines.py): no findings on the new copy. One pre-existing BAN-05 ("open source") warning inAboutClient.tsx:227exists onmaintoo, so it is out of scope here and reported to the coordinator.next build); CI builds it.