> For the complete documentation index, see [llms.txt](https://docs.originprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.originprotocol.com/yield-bearing-tokens/core-concepts/yield-collection-harvester.md).

# Yield Collection (Harvester)

Origin's yield-bearing tokens accumulate rewards through external strategies — validator incentives, lending market interest, liquidity provision fees, and token emissions from integrated protocols.&#x20;

These rewards accrue in different forms and locations and must be collected and converted to the protocol's base collateral before they can be reflected in holder balances through a rebase. This collection and conversion process is handled by the Harvester.

The Harvester is operated by a 2-of-8 multisig. Two Harvester contracts are deployed: a Standard Harvester for routine operations, and a CoW Harvester that routes swaps through CoW Protocol for improved execution quality and MEV protection. The appropriate contract is used based on the reward type and prevailing market conditions.

To automate and constrain harvesting operations, a Safe Module is layered on top of the multisig. The Safe Module validates each transaction before execution, enforcing that operators act within defined parameters: swaps must remain within acceptable slippage bounds, interactions are limited to verified assets, and DEX routing is restricted to approved protocols. This means the Harvester cannot be used to extract value or interact with unauthorized contracts, even in the event of a compromised multisig signer.

The Harvester is responsible for reward collection and conversion, not for triggering the rebase itself. Rebases are fired independently through Chainlink Keepers at least once per day, and anyone can call the rebase() function directly on the vault contract at any time. Underlying yield continues to accrue at the strategy level regardless of Harvester activity. A lapse in harvesting delays the point at which accumulated rewards are converted and reflected in holder balances, but does not halt yield\
generation.


---

# 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.originprotocol.com/yield-bearing-tokens/core-concepts/yield-collection-harvester.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.
