> For the complete documentation index, see [llms.txt](https://piggycell.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piggycell.gitbook.io/docs/piggycell-platform/challenge.md).
# Challenge
**Challenge-to-Earn** is Piggycell’s behavioral activation engine—a smart-contract-enabled mechanism that turns physical actions into on-chain missions, encouraging users to participate in the ecosystem beyond passive charging or ownership.
By introducing **time-bound, task-based, and socially driven challenges**, Piggycell creates an environment where real-world energy usage is gamified and linked to tokenized rewards.
**How It Works**
Users receive mission prompts or choose from open challenges via the Piggycell app or dApp interface. Challenges are defined by programmable conditions such as:
* **Frequency-based tasks**: “Charge 3 times this week”
* **Location-based tasks**: “Use Piggycell stations in 3 different districts”
* **Time-based missions**: “Charge during off-peak hours for 5 days straight”
* **Social quests**: “Refer 2 friends who complete their first charge”
Once the criteria are met, the activity is automatically verified through **on-chain event logging** and rewarded with:
* **PIGGY token payouts**
* **Limited NFT badge drops**
* **Ranking upgrades** (which unlock further tiers or staking benefits)
Smart contracts handle the challenge logic, ensuring trustless validation and reward distribution.
> Challenge-to-Earn makes the network feel alive. It transforms infrastructure interaction into a social, dynamic, and reward-driven experience.
***
**Key Benefits**
* **Increased User Engagement**\
Instead of one-time utility, users return regularly to participate in tasks—building habit loops and loyalty.
* **Gamified Retention Layer**\
Challenges can be personalized by region, time, or user profile—allowing Piggycell to drive behavior in targeted ways (e.g., increase usage in new cities or during low-demand hours).
* **Social Virality & Network Effects**\
Referral-based and leaderboard-integrated missions convert users into ambassadors—helping scale the ecosystem organically.
* **Token Demand Stimulation**\
Some challenges may require locking/staking PIGGY or holding specific NFT memberships—contributing to token velocity and lockup dynamics.
***
**Example Challenge**
> “Urban Explorer Challenge: Use Piggycell in 5 different neighborhoods within 7 days.\
> Reward: 15 PIGGY + limited-edition ‘City Nomad’ NFT badge.”
The user participates, sees their progress in the app, and receives instant on-chain confirmation upon completion—driving satisfaction and continued participation.
***
**Challenge-to-Earn transforms the Piggycell ecosystem from an infrastructure platform into a behaviorally optimized digital experience**, where every action counts, and every user becomes an active contributor to growth.
It turns energy consumption into a game—and participation into real value.
---
# 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://piggycell.gitbook.io/docs/piggycell-platform/challenge.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.