Methodology
How Trailblazer detects, scores, and surfaces emerging Solana ecosystem trends before they become obvious.
Pipeline Overview
Every fortnight, Trailblazer runs an automated pipeline that ingests live data from multiple sources, scores each protocol on momentum and novelty, clusters related signals into narratives, and generates actionable build ideas using AI. The entire process runs in under 5 minutes.
Data Sources
Onchain Activity
via Helius RPC
Transaction volume per program (current vs baseline)
Unique wallet estimation via transaction sampling
New wallet share and retention heuristics
47 tracked programs
Developer Activity
via GitHub API
Commit velocity (current vs baseline period)
Star growth and fork counts
New contributor detection and release tracking
47 tracked repositories
Twitter / X KOL Signals
via public RSS proxies
Core team: Toly, Raj Gokal, Solana Labs, Foundation
Protocol founders: Mert, Meow, Cindy, Lucas
VCs and research: Multicoin, a16z, Paradigm, Messari
91 KOL accounts monitored
News and RSS Feeds
public RSS/Atom feeds
Solana blog, The Block, CoinTelegraph, CoinDesk
Decrypt, Blockworks, Messari
Protocol-specific mention matching
8 RSS feeds per cycle
Scoring Formula
Each protocol is scored across three dimensions, then combined with novelty and quality adjustments.
Narrative Clustering
Top-scoring candidates are grouped into narratives using agglomerative clustering with cosine similarity on text embeddings.
Saturation Analysis
Each build idea is checked against a corpus of 150+ existing Solana projects to estimate market saturation. Cosine similarity between the idea description and existing project descriptions determines the saturation level: low (unique opportunity), medium (some competition), or high (crowded space). This helps founders focus on underserved areas.
AI-Powered Analysis
Kimi K2 (Moonshot AI) powers three key analytical steps with structured JSON outputs validated by Zod schemas.
Tracked Protocols (47)
Refresh Schedule
Reports are generated automatically on the 1st and 15th of each month via GitHub Actions cron. The pipeline can also be triggered manually via the admin API endpoint.