The AlphaTrace Methodology

How AlphaTrace surfaces early signals across development, research, news, and market expectations.

1. Signal Sources

AlphaTrace aggregates signals from four key layers of the crypto and AI ecosystem to identify emerging technologies, protocols, and research activity.

Developer Signals

GitHub Developer Protocol

Tracking newly created repositories and developer activity over the last 14 days across emerging technology sectors. This layer highlights early-stage protocols and developer momentum before they appear in mainstream market discussions.

Ecosystem Signals

Market News

Monitoring real-time industry developments via aggregated feeds from sources like CoinDesk and The Block, powered by the CryptoPanic. This layer captures protocol launches, funding announcements, and major ecosystem updates.

Research Signals

Research Hub (ArXiv)

Observing newly published technical papers related to blockchain, cryptography, and distributed systems. Academic research often reveals technological breakthroughs months before they reach production ecosystems.

Market Expectation Signals

Prediction Markets (Polymarket)

Tracking probability signals from prediction markets to understand collective expectations around major events and ecosystem outcomes. This layer provides insight into how market participants position around future scenarios.

2. Alpha Score

The Alpha Score is a developer velocity index (0–100) that reflects real-world engineering activity around a project.

"A star signals interest; a fork signals intent."

Unlike price, which is a lagging indicator, developer building activity is often one of the earliest signals of long-term ecosystem growth. When a developer forks a repository, they typically intend to experiment, modify, or build on top of it.

Because of this, forks are weighted more heavily than stars to prioritize genuine developer engagement over social attention.

To reduce short-term hype from extremely new repositories, a time normalization factor is applied.

Alpha Score Formula

SCORE = BASE(30) + ( (STARS × 0.5) + (FORKS × 2) ) / (DAYS + 3)
BASE (30) — a baseline signal weight
STARS — GitHub star count (community interest)
FORKS — GitHub fork count (developer intent)
DAYS — number of days since the repository was created

Forks are weighted 4× stronger than stars, reflecting the assumption that forks represent active experimentation or development. Projects with an Alpha Score above 85 are classified as high-heat signals, indicating unusually strong early developer momentum.

3. Signal Processing

After collecting raw signals from multiple sources, AlphaTrace processes the data through a filtering and scoring pipeline.

This stage removes irrelevant repositories, classifies projects into technology sectors, and evaluates developer momentum using the Alpha Score model.

Signal processing includes:

Noise filtering (junk repositories and non-crypto projects)
Project classification across emerging sectors
Developer activity analysis
Time-normalized scoring using the Alpha Score formula
© 2026 AlphaTrace Intelligence Engine Powered by Hermes Agent