# Why was Proof of Contribution created?

Proof of Contribution was created with the primary goal of enhancing accuracy when evaluating the impact of open-source software (OSS) projects. Traditional methods of assessing a project's impact often focus solely on the visible application layer, neglecting the contributions of underlying dependencies. This approach fails to provide a holistic view of a project's true value.

To address this limitation, Proof of Contribution was designed to quantify the impact of all projects across all open-source ecosystems. It assigns a dynamic score, known as a [project's teaRank](/tea/i-want-to.../learn-about-proof-of-contribution/what-is-tearank.md), based on the project's utilization within the broader open-source ecosystem over time. By considering the contributions of every dependency involved in a project, from top to bottom, Proof of Contribution allows each component to receive recognition for its contribution.

In addition to improving impact evaluation, Proof of Contribution aims to facilitate a fair and proportional distribution of rewards to contributors. An accurate assessment of the impact of a project and its dependencies allows rewards to be allocated accordingly and contributors to be fairly recognized and incentivized.

Proof of Contribution also tackles specific challenges faced by the open-source ecosystem. One such challenge is the issue of spam, where malicious actors manipulate the system to gain undeserved rewards. To counter this, the algorithm incorporates measures such as limits and reward thresholds. These strategies not only aid in spam detection but also introduce a cost to malicious actors, discouraging them from exploiting the ranking system.

Another challenge addressed by Proof of Contribution is the visibility of foundational software. Often, the focus is primarily on the visible application layer of a project, neglecting the critical contributions of foundational software. By considering the impact of all dependencies, Proof of Contribution allows foundational software to receive the recognition it deserves, promoting a more comprehensive understanding of a project's true value.

In summary, Proof of Contribution was created to enhance the accuracy of evaluating OSS project impact, allow fair and proportional distribution of rewards, and address specific challenges such as spam and the visibility of foundational software in the open-source ecosystem.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tea.xyz/tea/i-want-to.../learn-about-proof-of-contribution/why-was-proof-of-contribution-created.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.