# Season Timeline

DeCharge operates in structured release cycles called Seasons. Each Season marks a defined phase of growth in terms of device deployments, geographic expansion, onboarding mechanics, and reward distributions. This seasonal model creates transparency for contributors, enables feedback-driven iteration, and introduces new network participants in structured cohorts.

Unlike a traditional roadmap that progresses only by product features, Seasons allow us to evolve the network across three key vectors: scale, participation, and incentives.

## Objectives of the Season Framework

* Establish clear entry points for new hosts and contributors
* Align deployment milestones with manufacturing and logistics timelines
* Track key performance metrics (device uptime, session count, energy delivered)
* Distribute network rewards and incentives fairly, based on measurable contributions
* Iterate on operational policies, based on Season-specific learnings

## Season Milestones (2024 - 2026)

<table><thead><tr><th width="95.60003662109375">Season</th><th width="147.800048828125">Launch Window</th><th width="350">Highlights</th><th>Devices Deployed</th></tr></thead><tbody><tr><td>S1</td><td>Nov - Dec 2024</td><td>Initial Mini and Beast sales, Genesis community onboarding, reward pilot airdrop</td><td>154</td></tr><tr><td>S2</td><td>Q2 - Q3 of 2025</td><td>Delegated deployment scale-up, multi-country expansion, direct shipping for Beast</td><td>2,000+</td></tr><tr><td>S3</td><td>Q1 2026 (planned)</td><td>Titan pilot program, solar retrofit program, global demand map for delegated ops</td><td>Target: 5,000+</td></tr></tbody></table>

### Season 1: Genesis

* Marked the first public availability of DeCharge Mini and Beast devices
* Combined direct and delegated deployments
* Community participation launched with 40% of devices operated by individuals
* First iteration of the reward engine executed using off-chain tracking and tokenless reward points
* Revenue of $50,000+ generated via device sales
* Early hosts saw approximately 30% of their purchase returned via airdrops

### Season 2: Acceleration

* Introduced bundled delegated packs of 3 and 5 Minis for efficient scaling
* Expanded shipping regions to India, Southeast Asia, and the United States
* Real-time deployment map introduced for visualizing new opportunities
* Direct shipping for Beast model began, targeting fleet operators and property owners
* Shift toward regional logistics partnerships for faster lead times
* Refined onboarding workflows and pre-install documentation
* Season 2 operates with dynamic reward calibration to match real-world utilization and energy output

### Season 3 (Planned): Expansion and Specialization

* Focus on high-throughput deployments (Titan Mini, Titan, fleet hubs, highway nodes)
* Integration with solar and grid-balancing mechanisms
* Advanced reward engine with full on-chain telemetry scoring
* Launch of micro-funding and franchise models for community entrepreneurs
* Geo-targeted expansion into Tier 2 and Tier 3 cities globally
* Continued community governance pilots and cohort-based community onboarding

## Season-Based Participation Benefits

* Each Season comes with its own set of bonuses and referral programs
* Early participation in a Season may include device discounts, additional airdrops, or extended reward multipliers
* Participants retain long-term benefits (such as higher reward tiers) based on Season of entry
* Seasonal analytics help contributors optimize location, performance, and uptime


---

# 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.decharge.network/growth-and-roadmap/season-timeline.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.