# The Nomu Flywheel

**The Nomu ecosystem runs on two self-reinforcing loops.** \
\
One on-chain, driving reflexive demand for the [$NOMU](https://x.com/search?q=%24NOMU\&src=cashtag_click) token, and one off-chain, expanding the reach of the marketplace through real-world traction. 

Together, they form a hybrid flywheel where commerce powers buybacks, and value concentrates into [$NOMU](https://x.com/search?q=%24NOMU\&src=cashtag_click).\
\
**🟠 The Value Loop (inside-out).**

This is the economic flywheel that drives token reflexivity and sustained growth in attention, holders, and marketplace demand.<br>

<div data-with-frame="true"><figure><img src="/files/CUinXHOOLnJyAAtPUJIX" alt="" width="563"><figcaption></figcaption></figure></div>

1. Products sell out Each successful drop on Nomu generates qualified volume. A programmed slice of that volume is routed into a public reward pool.
2. Buybacks increase The reward pool is then used to buy[$NOMU](https://x.com/search?q=%24NOMU\&src=cashtag_click)on the open market. This creates natural buy pressure and aligns token movement directly with commerce activity.
3. New holders join[$NOMU](https://x.com/search?q=%24NOMU\&src=cashtag_click)buybacks fund loyalty distributions to the buyers that made a product drop a success. At the same time, sell-outs lift visibility and volume, drawing new wallets on-market, so holders grow from both earned distributions and second-order momentum.
4. Demand for drops grows Holding[$NOMU](https://x.com/search?q=%24NOMU\&src=cashtag_click)raises each participant’s loyalty status, which boosts their allocations in future drops. As the holder base grows, more capital competes for limited releases, tightening competition and driving faster sell-outs.

→ Back to “Products sell out”.\
&#x20;Every cycle compounds. Each sale strengthens the token. Each holder fuels the next sale.<br>

**🟢 The Demand Loop (outside-in).**

The second loop leverages Nomu’s phygital scale beyond Web3.

<div data-with-frame="true"><figure><img src="/files/Rln39KPrKJVVuEJxIGTi" alt="" width="563"><figcaption></figcaption></figure></div>

1. Products sell outSell-outs become cultural moments. Physical products travel, they are worn, shown, shared, so attention compounds beyond crypto and signals real traction on and off-chan.
2. Bigger collabsThis momentum attracts larger IPs, brands, and creators who see the power of community-led commerce on Nomu.
3. Retail flows inPartnerships pull in new eyes, audiences & consumers, allowing Nomu to scale horizontally & across industries.
4. New demand competesNew buyers crowd the same limited drops, pushing up competition. Reach expands, social proof compounds, sell-outs accelerate.→ Back to “Products sell out.”Each cycle widens reach, puts more eyes on the same limited releases, and makes sell-outs faster.

**🔁 Together: The Dual Engine of Reflexive Commerce**

<div data-with-frame="true"><figure><img src="/files/eeknXNdoGKihg9kSydxO" alt="" width="563"><figcaption></figcaption></figure></div>

While each loop can operate independently, their true power lies in how they interlock around the heart of this reflexive commerce model.&#x20;

From the outside, the demand loop brings in new brands, new product buyers, and fresh attention.&#x20;

From the inside, the value loop converts this new audience consumers into token holders and retains them with clear reflexive rewards.


---

# 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.nomu.dev/token/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.