# Pumpkin Seeds

### 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.

<figure><img src="/files/Rdp2tgDusckNSEvqbpbz" alt=""><figcaption></figcaption></figure>

### 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: 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:

```
GET https://docs.pumpkin.xyz/ecosystem/pumpkin-seeds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.