Tea Protocol

Start by connecting the code you already maintain. In the dashboard, link your repositories, verify control with a signed wallet message, and define what work gets paid: merged pull requests, reviewed issues, security fixes, documentation, design, testing, or release management. Assign weights, set payout cadence, choose a payout asset on Base, and publish the policy onchain so everyone can see how rewards are earned. From there, Tea watches the signals you selected and maps them to real contributors for automated distribution.

If you contribute to open source, the flow is simple. Sign in with your wallet, add your developer identities, and browse tasks that are already funded. Claim a bounty, open a pull request, and link it to the task. After maintainers review and merge, your reward is calculated and queued for payout with low fees and a verifiable receipt. Prefer retroactive funding? Submit claims pointing to commits, issues closed, docs you wrote, or packages you improved. Projects review in-app, and once approved, funds land in your address. You can track earnings across repos, export receipts, and receive notifications when anything updates.

For teams, DAOs, and sponsors, Tea turns budgets into outcomes. Allocate a pool, define windows for funding rounds, and let the engine apply your rules. Create milestone streams for roadmap items, require multiple reviewers or attestations for sensitive work, and cap payouts per cycle to control spend. Dashboards show who contributed, what shipped, and how much it cost—backed by an auditable onchain history for effortless reporting. Use the forum to propose updated weighting models, coordinate multi-repo campaigns, or settle edge cases with community input before payouts finalize.

Integrate Tea with the tools you already use. Fire webhooks from CI to trigger reward checks on merge, auto-label issues that are funding-eligible, and sync statuses back to your tracker or chat. Use the API to build contributor leaderboards, a sponsor portal, or internal analytics. Export CSV/JSON for accounting, or stream events into your data warehouse. This isn’t only for coders: writers can earn for tutorials and docs, planners for specs and backlog grooming, designers for assets and UX audits, and engineers for code, tests, and releases. Whether you maintain a single library or steward a multi-repo ecosystem, Tea gives you a repeatable, transparent way to pay for real work—onchain, on Base, and aligned with your project’s priorities.