How SourceCap
Verifies Value.
We bridge the gap between GitHub commits and market capitalization through a strict, trustless verification standard.
The Signal Noise
In the decentralized economy, anyone can launch a token and claim it represents a codebase or a project. This lack of verification leads to spoofed repositories, impersonation, and "vaporware" capital allocation. Investors have no on-chain guarantee that the token they buy is actually linked to the builders they believe in.
Cryptographic Linkage
SOURCECAP establishes a canonical link. We do not rely on manual claims. We query the immutable data of the Bags Protocol to verify that the GitHub user pushing the code is the same entity receiving the protocol fees (royalties).
Verified_Badge = TRUE;
} ELSE {
REJECT_SUBMISSION();
}
Developer Sovereignty
Our standard is strict: He who codes must control the capital flows. If a developer does not have claim over the Bags App royalties (e.g., in a hostile community takeover or unconnected launch), they cannot be verified on SourceCap. This ensures value flows back to the creators.
The Pulse Score
A real-time activity metric (0-100) that separates active builders from dormant projects. High pulse = consistent shipping.
Note: A low pulse doesn't mean a bad project. Mature, feature-complete codebases naturally have fewer commits. Pulse measures current activity, not project quality or long-term value.
Ready to prove your work?
Join the index of verified developer assets.