> For the complete documentation index, see [llms.txt](https://docs.chikn.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chikn.farm/tokens/worm/finding-worm.md).

# Finding $WORM

Just like $FEED, $WORM are earned as rewards in LP Farms. Staking LP tokens in the relevant pools on your FarmLand will earn you $WORM tokens, with the rate determined by the amount of LP staked and the FarmLand’s multiplier. Note that the multiplier for $WORM applies over a 120-day timeframe to ensure $WORM emissions are kept in check. This may be adjusted by the dev team over time. 

<figure><img src="/files/9E9Rt9o6DnJeT9q7aTlf" alt=""><figcaption><p>LP Farm with the $WORM silo displayed to the right</p></figcaption></figure>

FarmLand have a dedicated silo for $WORM that, once filled, stops accumulating additional tokens. Players can empty their silo at any stage or increase the Bigness of their FarmLand to also increase silo capacity. Note that once FarmLand reaches 120 Bigness, silo capacity becomes unlimited.

For more information, see the section on [Farming](/gaming/farming.md).


---

# 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.chikn.farm/tokens/worm/finding-worm.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.