> For the complete documentation index, see [llms.txt](https://docs.handle.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.handle.fi/rewards/paused/quests/protocol-incentive-experiments.md).

# Protocol Incentive Experiments (PIEs)

{% hint style="info" %}
most PIEs have been deprecated and transitioned to [Zealy](https://zealy.io/c/handlefi/questboard) so please check before completing PIEs. There is more information about Zealy quests [here](https://app.gitbook.com/o/-MiswpCSPU5ZH4S1SDDG/s/-MUR8MivZ356lgVw_jq_-887967055/~/changes/1483/rewards/quests).
{% endhint %}

one of the primary reasons for adding tokenomics to any protocol design is to create incentives to drive and maintain protocol growth and success

liquidity mining rewards is now a staple of DEFI, and bounties are also commonly used.\
\
so, in addition to platform rewards, handle.fi will be exploring a range of Protocol Incentive Experiments, or PIEs designed to further incentivise protocol users to contribute to and benefit from any protocols success

[**PIE #1** - retweet community content to earn $FOREX](https://docs.handle.fi/rewards/protocol-incentive-experiments/incentive-experiment-1).\
[**PIE #2** - create **handle** memes to help grow community awareness](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-2-memes).\
[**PIE #3** - support the handle troop by adding (42,🦍) and win](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-3-weekly-bonus)!\
[**PIE #4** - produce rich content to explain and inform.](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-4-content-production)\
[**PIE #5**](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-5-referrer-program) - refer new members to our [**discord**](https://discord.gg/nbSdYCDGhh) community.\
[**PIE #6** - engage in community conversation and support](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-6-troop-participation-program).\
[**PIE #7**](https://docs.handle.fi/rewards/protocol-incentive-experiments/pie-7-convert-rewards)**\_b** - exchange tokens using [**handle convert** ](https://app.handle.fi/convert)and win $FOREX<br>

{% hint style="info" %}
**participants can record their contribution here:** \
\
<https://docs.google.com/forms/d/e/1FAIpQLSepAMnD8OteN93Mtz3d3xXvIajdQWL86aT0da8zZgLb3Te1Lw/viewform>
{% endhint %}

**all rewards can be viewed here:**\
\
<https://docs.google.com/spreadsheets/d/13UZFF_HmIPim0xZK2fXhYi5L9v63xHZYb4x2fZYvFys/edit?usp=sharing>


---

# 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://docs.handle.fi/rewards/paused/quests/protocol-incentive-experiments.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.