> 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/charge-to-earn.md).

# Charge to Earn

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

The **Charge-to-Earn** mechanism is Piggycell’s entry point for mainstream user adoption—a model that transforms the act of charging a device into a **rewardable, trackable, and blockchain-registered economic action**.

In a world where charging is ubiquitous yet economically invisible, Piggycell gives value to micro-energy consumption events by linking them to an **on-chain incentive system** powered by the PIGGY token.

**How It Works**

Every time a user charges their smartphone or other device using a Piggycell-enabled node (e.g., portable battery, wall-mounted dock, micromobility station), the activity is:

* **Recorded on-chain** with a timestamp, location, and device ID
* **Matched against predefined smart contract conditions** (e.g., time-of-day, location tier, usage frequency)
* **Rewarded in PIGGY tokens** proportional to the energy dispensed, the activity context, or gamified multipliers

Users simply plug in, and behind the scenes, their participation is verified, logged, and rewarded—creating a **seamless Web2-to-Web3 experience**.

> With Charge-to-Earn, users no longer just “use” infrastructure—they interact with it economically.

**Key Benefits**

* **Incentivized Behavior at Scale**\
  By rewarding even the smallest actions (a 10-minute phone charge, for example), Piggycell encourages daily interaction and long-tail network engagement.
* **Web3 Onboarding Through Real-World Behavior**\
  Users earn PIGGY tokens without needing prior crypto knowledge. Physical interaction becomes their first wallet action, enabling a smoother transition into the ecosystem.
* **Gamification Potential**\
  Charge-to-Earn can support mission-based incentives, social challenges (e.g., “Charge 5 times this week”), or seasonal reward multipliers—enhancing retention and viral growth.
* **Token Utility + Circulation**\
  Earned tokens can be spent within the Piggycell ecosystem (e.g., membership NFTs, discounts, governance), used externally, or staked for further rewards—closing the economic loop.

**Real-World Use Case**

A commuter in Seoul connects their phone to a Piggycell station during rush hour. The system recognizes it as a high-demand location/time and applies a bonus multiplier. The commuter receives PIGGY tokens in their app wallet instantly, which they later redeem for a discounted monthly pass NFT.

***

**Charge-to-Earn is not just a marketing hook—it is a protocol-native user acquisition engine**, bringing millions into Web3 not through speculation, but through meaningful, repeatable, real-world activity.

It makes charging profitable—not just for the infrastructure owner, but for the user too.


---

# 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/charge-to-earn.md?ask=<question>&goal=<endgoal>
```

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