> For the complete documentation index, see [llms.txt](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/tokenomics-and-incentives/incentive-model.md).

# Incentive Model

As the nature of web3 is global and borderless by philosophy and design, we strongly believe in the ability of a decentralized model to incentivize and reward positive behaviors in a global ecosystem. Consumer privacy limitations vary from country-to-country, and we assert that a protocol encouraging consent, control, and ownership will have an objective positive effect on the internet as a whole.

That global humans make up the internet is undeniable; so too must we create avenues for our scope of participation and development to reach that global community. We believe in global incentive models that have the potential to create positive externalities for the broader internet ecosystem – by creating a global mesh of publicly certified content attributed to their rightful owners and affirmatively permissioning content of all categories, we can bring the power of consent and consent-enabled applications to every human that has internet access.

## Proposed Incentives

We believe a proper incentive model has the potential to create positive externalities such as increased human user verification (less effective malicious bots), increased trust between platforms and contributors, a better relationship between content origination and attribution, and faster remediation of non-consensual content.<br>

Our proposed incentive model would reward users for the following activities:

* **Node functionality**
  * IPFS node and node validators are rewarded for increasing the storage capacity dedicated for PLP-pinned content. Additionally, second and third-order effects include expanding our customer reach, lowering our cost model, and expanding the IPFS/Filecoin ecosystem, encouraging the usage of decentralized peer to peer storage systems.
* **Public computing & bounty**
  * Community members that run public Privy nodes participate in decentralized domain detection utilizing public machine learning model weights; detection escalated successfully results in a network reward.
  * Community members are rewarded for manually reporting unverified or stolen content on a network or platform.
    * Note: Community members with this access are vetted through an application/reputation process in order to ensure the safety of all members and reduce bad actors who may be targeting a single creator or account.&#x20;
    * Accepted community members are then given a non-transferable proprietary token that provides them access to this benefit.
* **Author authentication & verification**
  * Creators are rewarded for participating in authentication activities to ensure their related identity on-chain is tied to a living human being, reducing the instances of bots and bad actors cluttering the system.
    * Note: For our user type, Zero Knowledge proof typing for KYC is of the utmost importance as we do not want to put the user’s real identification information in the position of being unmasked or revealed i.e. birthdate, location, home address, legal name.
* **Photo Securitization**
  * Creators who use the Privy Labs Protocol to pin content to the system (via our PrivyCam app or otherwise) are rewarded for participating in securing their content; this is measured as a ratio of Privy content to non-Privy content on a given sampled public domain, further incentivizing the usage of protocol proxies to engage with non-protocol-conformant applications/domains.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/tokenomics-and-incentives/incentive-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.