> For the complete documentation index, see [llms.txt](https://hoodstrategy.gitbook.io/hoodstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hoodstrategy.gitbook.io/hoodstrategy/readme.md).

# Hold. Earn. Repeat.

The first strategy token that accumulates real tokenized Robinhood stock and pays it to holders.

<p align="center"><img src="https://1537799159-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtZXnYH1NJckNq4i7Mk7r%2Fuploads%2FVds2GQpha5JNgqMRuiy5%2Flogo%20transparent.png?alt=media&amp;token=988be22e-66f6-46c0-967d-2c5872347091" alt="" data-size="original"><br><br><strong>HoodStrategy</strong> turns trading activity on its own token, <strong>$HOODSTR</strong>, into an accumulation of real exposure to Robinhood stock, automatically paid out to everyone who holds the token.</p>

You hold **$HOODSTR**. The protocol buys tokenized Robinhood stock (**HOODX**) for you. You claim it whenever you want.

***

## The thesis

Most tokens do nothing. They rise and fall on speculation alone and never produce anything tangible for the people who hold them. HoodStrategy inverts that logic.

Every buy and every sell of $HOODSTR pays a **5% tax**. That tax is automatically converted into **HOODX** tokenized Robinhood stock, backed 1:1 by real shares held in custody and the HOODX is distributed to all $HOODSTR holders, pro rata to their holdings.

The result is a **flywheel**: more volume means more Robinhood stock bought, which means more paid out to holders, which attracts more participants. Everything happens **on-chain, automatically, and verifiably**, powered by Uniswap v4.

{% hint style="info" %}
**New here?** Start with [Overview](/hoodstrategy/readme/overview.md) for the fastest mental model, then read [How It Works](/hoodstrategy/how-it-works.md) for the mechanics.
{% endhint %}

***

## Three pillars

**A real asset.** The protocol doesn't accumulate an abstract token it accumulates HOODX, backed by real Robinhood shares held in custody. Tangible exposure, not a promise.

**A trustless mechanic.** Tax collection, the HOOD purchase, and distribution all happen in a single on-chain transaction, using Uniswap v4 hooks. No mandatory central bot, no manual step inside the loop.

**Full transparency.** 100% on-chain treasury, verified contracts, locked ownership, a hard-capped tax, and a public real-time dashboard. Every dollar of stock bought is verifiable on-chain.

***

## At a glance

|             |                                       |
| ----------- | ------------------------------------- |
| Token       | **$HOODSTR**                          |
| Reward      | **HOODX** (tokenized Robinhood stock) |
| DEX         | Uniswap v4                            |
| Tax         | 5% buy / 5% sell                      |
| What you do | Hold. Everything else is automatic.   |

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hoodstrategy.gitbook.io/hoodstrategy/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
