# Value Accrual Flywheel

The table below maps platform growth events to their corresponding token mechanic and supply effect.

| Platform Growth Event               | Mechanism Activated                                     | Supply / Demand Effect                              |
| ----------------------------------- | ------------------------------------------------------- | --------------------------------------------------- |
| User pays subscription in $EITHER   | Subscription burn (10%)                                 | Circulating supply decreases                        |
| Marketplace transaction completed   | Marketplace fee burn (10%)                              | Circulating supply decreases                        |
| App token launched via Launchpad    | LP lock (1-5 yrs) + launchpad fee burn (20%)            | Supply locked; fees generated from same event       |
| Swaps on launched app tokens        | Locked LP earns trading fees                            | Protocol earns while supply is constrained          |
| Platform revenue grows              | Buyback and lock (up to 35% of net revenue after costs) | Open market supply tightened                        |
| Builders stake for launchpad access | Tokens removed from circulation                         | Supply reduced; demand driven by access requirement |
| Creators stake for marketplace      | Tokens removed from circulation                         | Staking demand independent of build activity        |
| Builder reputation compounds        | Sustained $EITHER engagement required                   | Long-term non-speculative demand                    |
| Creator ecosystem expands           | More marketplace transactions, more burns               | Burn surface grows with platform scale              |

> The flywheel activates on usage. Not on price. Not on new buyers. Each mechanism generates supply pressure as a direct, automatic output of platform activity.


---

# 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.eitherway.ai/token/appendix/value-accrual-flywheel.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.