> For the complete documentation index, see [llms.txt](https://docs.touchgrass.today/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.touchgrass.today/02-harvest.md). # Harvest Harvest is Touch Grass's seasonal staking program for $TOUCHGRASS. Live at [harvest.touchgrass.today](https://harvest.touchgrass.today). ## How It Works Harvest runs in **seasons**. Each season has its own planting window, harvest date, minimum deposit, and reward pool — configured independently, never a fixed APY. 1. **Plant** — deposit $TOUCHGRASS during the planting window. Repeat deposits during the same window top up your existing position rather than creating a new one. Once the planting window closes, no further deposits or top-ups are accepted for that season — your position is locked in as-is. 2. **Wait** — your deposit stays reserved to you until the harvest date. 3. **Claim** — once the season reaches Harvest Ready status, claim your principal back. 4. **Rewards** — distributed separately from principal. Users can participate across multiple seasons, and harvest history remains permanently viewable. ## Future Seasons Every Harvest season is configured independently — its own deposit window, harvest date, minimum deposit, reward pool, and eligibility rules. This is by design, not a limitation: expect terms to vary season to season rather than repeat past seasons exactly. Also under consideration: specific traits from Screen Touchers or Grass Touchers NFTs could add bonuses to a planter's Harvest rewards — possibly including Summer Season 2026, not just future seasons. This is exploratory and not yet confirmed. ## Reward Distribution Each season's reward pool is split: | Share | Goes to | | ----- | ----------------------------------------------------------------------------- | | 70% | Proportional to deposit size | | 20% | Random planters (equal chance per unique planter, regardless of deposit size) | | 10% | MVPs | ### Example Payouts These are illustrative examples using round numbers — actual payouts depend on the real reward pool and total participation each season. Say a season's total reward pool is **1,000,000 $TOUCHGRASS**, split 700,000 / 200,000 / 100,000 across the three pools, with 10,000,000 $TOUCHGRASS planted in total across 200 unique planters. * **Small planter (minimum deposit, 50,000 planted = 0.5% of total planted):** Proportional share alone = 3,500 $TOUCHGRASS. They also have the same shot at the random pool as everyone else — if 20 random winners are drawn from 200 planters, that's a 10% chance at an additional 10,000 $TOUCHGRASS. * **Large planter (500,000 planted = 5% of total planted):** Proportional share alone = 35,000 $TOUCHGRASS — ten times the small planter's, since this pool scales with deposit size. Same 10% random-pool odds as everyone else, worth the same additional 10,000 $TOUCHGRASS if selected — deposit size doesn't improve those odds. * **MVP:** If 5 MVPs are recognized for the season, each receives 20,000 $TOUCHGRASS from the MVP pool — on top of whatever they earned proportionally from their own deposit. * **Best case:** A single planter could stack all three — proportional share on their deposit, a random-pool win, and an MVP payout — since the pools are independent and not mutually exclusive. ## Summer Season 2026 — "Plant Today. Harvest Tomorrow." | Parameter | Value | | ----------------- | -------------------------- | | Planting window | Aug 1, 2026 – Aug 31, 2026 | | Harvest date | Mar 1, 2027 | | Minimum deposit | 50,000 $TOUCHGRASS | | Deposit increment | 50,000 $TOUCHGRASS | Summer Season 2026 is open for planting now. Users can see what they've planted at any time and claim their principal back once the season reaches Harvest Ready status. ## Planting Strategies A few approaches, depending on what you're optimizing for: * **Maximize proportional share** — the 70% pool pays out relative to deposit size, so planting as much as you can affords the biggest slice of that portion. Best if you're planting a large position anyway. * **Maximize random-pool odds** — the 20% random pool gives every unique planter equal odds regardless of deposit size. Planting exactly the minimum (50,000 for Summer Season 2026) gets you the same shot at that pool as a much larger deposit, so it's an efficient way to be "in the running" without committing more $TOUCHGRASS than necessary. * **Multi-season spread** — since you can participate across multiple seasons and each has independent terms, spreading deposits across seasons (rather than going all-in on one) diversifies exposure to different reward pools and timelines instead of locking everything to a single harvest date. * **Top-up as you go** — repeat deposits top up your existing position, so you don't have to commit the full amount upfront. Plant the minimum early to lock in eligibility, then add more before the planting window closes if you decide to increase your position — once the window ends, deposits are no longer accepted, so any top-ups need to happen before then. --- # 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.touchgrass.today/02-harvest.md?ask=&goal= ``` `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.