HoodScan
How It Works
HoodScan scans GitHub for projects built on and around Robinhood Chain, scores their momentum, and ranks the top 50. Here is how a repo goes from first commit to the leaderboard.
Scanning GitHub
- HoodScan crawls GitHub for repos that touch Robinhood Chain
- It looks for chain IDs, RPC endpoints, contract calls, and ecosystem SDKs
- Matches range from dApps and infra to trading bots and RWA tooling
- Each detected repo is indexed, categorized, and queued for scoring
The HoodScan Score
- Every indexed repo gets a score built from stars, commit activity, and Boosts
- Recent activity counts more than old stars, so momentum beats size
- Each repo also carries a tier reflecting how deep it goes into the chain
- Scores recompute on every scan, so the ranking tracks real movement
Boost Mechanics
- A Boost is a public vote of conviction in a repo
- Anyone can Boost a project straight from its listing
- Boosts feed into the HoodScan Score alongside GitHub signals
- Recent Boosts count for more, so support has to stay current
Top 50 Leaderboard
- The 50 highest-scoring repos make the board
- Positions shift as scans complete, not on a fixed schedule
- Filter by category, from Chain Core to Trading Bots
- Repos that go quiet lose ground and drop off
Categories & Tiers
- Every repo lands in one of 14 categories, from dApps to Node Ops
- Categories keep niche tools from being buried
- Tiers mark how close a repo sits to the chain itself
- Core protocol work carries more weight than wrappers
Always Up to Date
- Scans run continuously against the GitHub API
- Star counts, commits, and Boosts refresh on every pass
- Rankings move as soon as new signals land
- No submissions needed. If it is on GitHub, HoodScan finds it