Tea Protocol

Automate open-source rewards on Base with rules, sponsor vaults, and easy claims.
Rating
Your vote:
Notify me upon availability
Info updated on:

Open-source work doesn’t have to rely on applause alone. With Tea Protocol, you can set up a predictable, auditable flow of value to the people who keep your code alive. Start by connecting a wallet on the Base network, creating a project entry, and linking your repositories. Define what counts as eligible work—merges, releases, security fixes, documentation, triage—and set how funds should be split (by contributor weight, by component, or by milestone). Add a funding source (sponsors, grants, or your team’s budget), choose a payout cadence, preview a dry run, and publish the rules. As contributions are recognized, Tea tracks them and prepares on-chain distributions you can confirm in a click. Contributors claim directly from the contract; you get transparent records without manual spreadsheets.

Individual developers use Tea Protocol to turn everyday teamwork into income without changing their workflow. Create a contributor profile, connect your identity (e.g., GitHub), and opt into the projects you touch. Keep building as you normally do—open PRs, review code, write tests, fix bugs, improve docs. Tea indexes activity you’ve consented to share and calculates your share when a payout window closes. You’ll see pending rewards, gas estimates on Base, and per-project claim history. Set alerts for new funding rounds, upcoming distributions, or bounties that match your skills. If you maintain multiple repos, group them and route payouts to different addresses for taxes or team splits. more

Screenshot (1)

Review summary

Features

  • On-chain payouts on the Base network with low fees
  • Project registration and repo linking
  • Contributor identity and verification (e.g., GitHub linkage)
  • Rule-based allocation by activity, component, or milestone
  • Sponsor vaults, grants, and bounty workflows
  • Automated contribution indexing and dry-run previews
  • Claim interface with per-project histories and receipts
  • APIs, webhooks, and CI integration support
  • Multi-sig approvals and audit-friendly exports
  • Community coordination via the forum

How It’s Used

  • Maintainers: define reward rules, fund pools, and automate releases
  • Individual contributors: link identity, earn from PRs, reviews, docs
  • Sponsors/foundations: allocate budgets across dependencies and grants
  • Teams/DAOs: run recurring payouts, require approvals, and track impact
  • Security: weight fixes higher, post targeted bounties, pause during incidents
  • Documentation and community: map labels/paths to payouts for non-code work
  • Integrators: use APIs/webhooks to sync releases and automate eligibility

Comments

User

Your vote: