> For the complete documentation index, see [llms.txt](https://beraborrow.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://beraborrow.gitbook.io/docs/pollen/why-hold-pollen.md).

# Why hold POLLEN?

🟠 As the adoption of Beraborrow grows, so does the need for POLLEN

🟠 All interest rate revenue contributes to governance driven incentives within the ecosystem. Distributed via sPOLLEN (staked POLLEN) rewards vault to support active participation in Berachain’s Proof of Liquidity.

🟠 By staking POLLEN, you actively participate in Beraborrow’s governance and ​​participation rewards tied to governance activities.

🟠 Upon a successful vote, 60% of protocol fees are allocated to governance initiatives determined by vePOLLEN holders (ve means vote escrow, longer term lockup). Incentivising active participation in protocol decision making.&#x20;

🟠 A structured governance-driven distribution model facilitates iBGT swaps for POLLEN.

🟠 vePOLLEN holders also control the VE treasury which accumulates, BGT, Infrared governance, and iBGT to POLLEN swaps.&#x20;

🟠 POLLEN’s governance role strengthens as protocol activity and participation increase.


---

# 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://beraborrow.gitbook.io/docs/pollen/why-hold-pollen.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.
