Repository navigation
Whitelist: replace "in superblock" count with project-by-project "active" count - #452
Merged
barton2526 merged 1 commit intoJun 5, 2026
Conversation
…ive" count The summary header showed "Whitelisted Projects: N (M in superblock)", where M was sb.total_projects from the superblock contract. That count includes manually-greylisted projects whose scraper-converged stats still landed in the superblock with Mag=0, so the headline overstated how many projects are actually earning rewards. On the live data today the cell read "16 (15 in superblock)" while only 11 projects are active and accruing. Replace the parenthetical with a project-by-project active count: 16 (11 active) The new count filters on projectStatus(p).cssClass === "status-active", which already maps both plain "Active" (in_superblock=true) and "Active by Greylist Override" to status-active, and routes "Active + in_superblock=false" to status-excluded. It cannot be derived as "in_superblock − greylisted − excluded" because the greylisted and excluded sets can overlap (a manually-greylisted project whose host is also scraper-unreachable shows up in both registries), so a project-by-project filter is the only correct computation. Co-Authored-By: Claude Opus 4.7 <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
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.
Summary
Whitelisted Projects: N (M in superblock), whereMissb.total_projectsstraight from the superblock contract. That count includes manually-greylisted projects whose scraper-converged stats still landed in the superblock withMag=0, so the headline overstates how many projects are actually earning rewards. On the live data today the cell reads16 (15 in superblock)while only 11 projects are accruing.16 (11 active).projectStatus(p).cssClass === "status-active", which already maps both"Active"(within_superblock=true) and"Active by Greylist Override"tostatus-active, and routes"Active" + in_superblock=falsetostatus-excluded. So one filter pass picks up exactly the active-and-in-superblock projects.Why it can't just be
in_superblock − greylisted − excludedThe greylisted set and the excluded-by-scrapers set overlap. A manually-greylisted project whose stats host is also unreachable (e.g. SiDock@home on mainnet today — site hard-down, picked up by
convergencereport'sexcluded_projects) is both greylisted and excluded by scrapers. Set arithmetic on the aggregate counts double-counts that project; the only correct computation is project-by-project.Test plan
http://jco-linux.jcowens.net:81/whitelist.htmshowsWhitelisted Projects 16 (11 active)on current mainnet data (11Active by Greylist Override, 4 manually-greylisted-but-in-superblock, 1 manually-greylisted-and-unreachable).🤖 Generated with Claude Code