tea Protocol primary sources — 2026-05-09

What I reviewed

• Official overview:
  • https://tea.xyz/learn/overview
• Official white paper:
  • https://docs.tea.xyz/tea-white-paper/white-paper
• Official repository:
  • https://github.com/teaxyz/white-paper
  • https://raw.githubusercontent.com/teaxyz/white-paper/main/white-paper.md

Key takeaways from primary sources

• tea’s main mechanism is not just “pay maintainers.” It tries to combine dependency-graph importance, contributor/project reputation, staking, slashing, and dispute handling into one protocol for OSS maintenance.
• The overview page’s framing around the “Nebraska Problem” is useful because it makes clear that tea is targeting invisible but critical maintainers rather than only popular repos or visible builders.
• The white paper says rewards flow to registered projects according to Proof of Contribution / teaRank, which means the decisive governance question is how project importance gets measured and updated.
• tea is more ambitious than a grant platform because it adds behavioral enforcement: package issues can be challenged with evidence and can lead to slashing.
• The move to an OP Stack Layer 2 matters analytically. tea is trying to own the execution environment for its incentive system rather than simply deploy contracts inside another ecosystem’s app layer.
• The GPG precompile and GPGRewardWallet design are the most distinctive technical ideas surfaced in this pass. They import developer-native identity/signing habits into smart-contract account control and make tea more interesting than a standard wallet-plus-token rewards app.
• Compared with SourceCred or Open Source Observer, tea pushes harder toward payout and protocol enforcement. The same measurement layer that decides legibility is meant to drive direct economic rewards and governance consequences.

Specific source signals worth retaining

• Overview page: strongest concise articulation of the “why now” and the project’s focus on hidden dependency maintainers.
• White paper abstract and introduction: best explanation of Proof of Contribution, package registration, contributor/project reputation, and slashing logic.
• Architecture section: important for the OP Stack migration, fraud-proof security assumptions, sequencer model, and dedicated execution environment.
• GPG precompile section: the standout mechanism detail; it shows tea is attempting to link open-source identity infrastructure to onchain control in a nontrivial way.

Why this entry belongs in the corpus

• It strengthens the contributor-legibility cluster with a project that turns dependency significance into direct onchain rewards rather than just analytics or peer recognition.
• It is a useful comparison class for SourceCred, Open Source Observer, Drips, and Hypercerts because it ties together legibility, rewards, identity, and enforcement in one stack.
• The reusable insight is that OSS funding systems can centralize power in impact scoring, registry inclusion, dispute evidence, and identity linkage even when they present themselves as neutral reward distribution protocols.