Summary: tea Protocol is best understood not as a generic tokenized OSS rewards app, but as an attempt to turn package-maintainer importance, contribution history, package-security review, and developer identity into a single incentive and governance stack. Its primary materials describe a registry of software projects, a Proof of Contribution / teaRank system for measuring ecosystem importance, staking and reward flows, reputation that spans projects and contributors, slashing for security or quality failures, and an architectural shift from dApp to dedicated OP Stack Layer 2. That makes it a useful comparison class for SourceCred, Open Source Observer, Drips, Hypercerts, and other systems where the real question is how software labor becomes legible, who defines impact, and which control surfaces decide how maintenance gets funded and disciplined.
What it does:
Registers open-source projects and package maintainers into a protocol-level system intended to reward software that is important to the wider dependency graph
Uses a Proof of Contribution / teaRank model to estimate project impact and distribute rewards based on contribution to ecosystem utility and health
Adds staking and slashing around projects so package quality, integrity, and dispute processes become part of the incentive system rather than pure retrospective analytics
Introduces a reputation layer spanning both projects and contributors instead of treating each package as an isolated rewards target
Recasts the system as an OP Stack-based Layer 2 so reward claims, staking, governance, and related actions live on a dedicated chain rather than only as an app on another rollup
Uses a GPG precompile and GPG-linked smart-contract wallets to tie familiar developer cryptographic identity practices to onchain actions
Key claims:
The overview page frames tea around the “Nebraska Problem” and dependency mapping, which is the clearest concise statement that the project wants to reward infrastructure maintainers who are deeply relied on but poorly recognized
The white paper makes the main mechanism explicit: registered projects receive rewards based on Proof of Contribution, while network participants can also challenge packages and trigger slashing when supported claims reveal security or development issues
The migration from dApp to OP Stack Layer 2 is analytically important because tea is no longer just a rewards formula sitting on another chain; it is trying to become a specialized execution environment for OSS incentive, identity, and governance flows
The GPG precompile is one of the project’s most distinctive mechanism choices. Rather than treating wallet keys as the only identity primitive, tea tries to import existing developer trust infrastructure — PGP/GPG keys used for code signing and release verification — into smart-contract control and authentication
The white paper’s combination of rewards, staking, package review, slashing, and contributor/project reputation means tea is trying to govern software supply-chain behavior, not only subsidize maintainers after the fact
tea is a strong comparison case for SourceCred and Open Source Observer because it moves from measurement into enforcement and payout: dependency significance is meant to determine direct onchain rewards and governance consequences, not just produce analytics
The project’s architecture suggests that the decisive governance surface will sit upstream of payouts: in registry inclusion, dependency mapping, impact scoring, trusted evidence in disputes, and the operational control of the L2 stack itself
Whitepaper: The core primary source for this pass was the official tea white paper plus the protocol overview page; see ../whitepapers/tea-protocol-primary-sources-2026-05-09.md.