> For the complete documentation index, see [llms.txt](https://docs.pumpkin.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pumpkin.xyz/ecosystem/pumpkin-seeds.md).
# Pumpkin Seeds
Pumpkin Seeds are the system that ties traders, creators, and incentives into one coherent economy.
### Season model
**Season 1:** approximately 12 weeks\
**Accounting cadence:** weekly\
**Distribution day:** every Tuesday, based on the prior week’s contribution
This weekly rhythm creates predictable engagement and allows users to plan behavior around a clear incentive calendar.
### Four contributor classes
Seeds primarily reward four categories of contribution:
#### (1) Real traders: genuine fills and long-term activity
Pumpkin seeds reward sustained, real activity rather than superficial volume.
#### (2) Loss subsidy: weekly net-loss users receive pumpkin seeds
Users with net losses in a week receive Seeds subsidies to reduce attrition and encourage learning. This is a deliberate retention mechanism: it turns losses into a continuing relationship rather than an exit point.
#### (3) Liquidation subsidy: controlled and capped
Rules:
* at most one liquidation subsidy per week
* at most three times per season per user
This is designed to reinforce risk awareness, not encourage reckless leverage.
#### (4) Streaming rewards: high-quality creators and active rooms
Seeds reward creators who produce valuable content and drive meaningful activity. Metrics can include active viewer minutes, retention, strategy usage, and verified engagement.
### Weekly transparency as a product requirement
Pumpkin seeds must not feel like a black box. A formal Seeds UI should show:
* weekly breakdown by category
* why the user qualified
* what actions improve next week’s score
### Seeds buyback program (coming soon)
Pumpkin will allocate a portion of platform profits to buy back pumpkin seeds. This creates two potential pathways for users:
* holding pumpkin seeds for future TGE conversion, and
* selling pumpkin seeds through buyback-driven demand.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pumpkin.xyz/ecosystem/pumpkin-seeds.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
