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

# Introduction

> **"THE ROOST IS ALIVE. IT'S COMPLETE."**

Welcome to **HOODROOST**, a next-generation Web3 Game-Fi ecosystem built on the **Robinhood Chain**.

HOODROOST is not a generic NFT dashboard. It is an immersive, living game world where community, gamified yield loops, digital collectibles, and real blockchain infrastructure merge into a singular experience.

***

## 🦅 The Core Concept

In most Web3 projects, users open a transactional interface and check floor prices. In HOODROOST, the user's mental experience is:

> *"I just stepped through the heavy wooden doors and entered a living world."*

Behind the atmosphere is a high-performance GameFi engine that powers:

1. **Catch the Eggs — Live Farm Game**: A real-time, skill-based arcade game where players catch falling eggs for $EGGS rewards, amplified by their NFT Roost Power multiplier.
2. **Roost Power Multipliers**: Digital collectibles (Hoodroosts NFTs) that mathematically multiply every egg caught — displayed live as a ⚡ HUD badge during gameplay.
3. **Passive Farm Engine**: Continuous background egg accumulation with a 24-hour vault cap as a secondary yield layer.
4. **Incubator Arena**: High-stakes egg hatching mechanics powered by verifiable server-side probability matrices.
5. **Streak Multipliers & The Flock**: Daily engagement fire bonuses and exponential referral flock trees.
6. **Auditable PostgreSQL Ledger**: Every egg earned, spent, or caught is permanently recorded in an immutable ledger with zero mock data.

***

## 🌐 Quick Protocol Specs

| Specification                   | Details                                      |
| ------------------------------- | -------------------------------------------- |
| **Project Name**                | **HOODROOST**                                |
| **Future Token**                | **$ROOST**                                   |
| **In-Game Reward Currency**     | **$EGGS** (Points)                           |
| **NFT Collection**              | **HOODROOSTS / Birds**                       |
| **NFT Contract (Mainnet)**      | `0x6d9905cfbc6ff15784ab6dcf113f62b18252ee1a` |
| **Primary Network**             | **Robinhood Chain (Mainnet)**                |
| **OpenSea Verified Collection** | <https://opensea.io/collection/h00d--r00st>  |
| **Game World**                  | **The Roost**                                |
| **VIP Pass**                    | **Roost Pass**                               |

***

## 🏛️ Ecosystem Structure

```mermaid
graph TD
    A[Hoodroost NFT Collection] -->|Single-Bind Invariant| B[Roost Power Engine]
    B -->|⚡ Multiplies Every Egg Caught| C[Catch the Eggs — Live Farm Game]
    C -->|Skill × Roost Power = $EGGS| D[Player Egg Balance]
    D -->|Sink: 500 Eggs| E[Egg Incubator Arena]
    E -->|Common / Rare / Epic / Mythic| D
    D -->|Converts At TGE| F[$ROOST Future Governance Token]
    G[Flock Referrals] -->|500 Eggs / Inviter + 250 / Invitee| D
    H[Daily Streak Fire] -->|Daily Exponential Bonus| D
    I[Passive Farm Engine] -->|Background Accumulation| D
```

***

## 🧭 Navigation

* Read [The Lore of The Roost](/h00d-r00st-1/lore.md) to understand the subterranean origins of the Flock.
* Explore [Game-Fi Architecture](https://github.com/Jamezyair1/hoodroost/tree/main/docs/gamefi-mechanics.md) for detailed mathematical breakdowns of yield curves and incubator drops.
* Discover [Tokenomics](/h00d-r00st-1/tokenomics.md) to understand how $EGGS points transition to the $ROOST token.
* Review [Security Architecture](/h00d-r00st-1/security.md) for details on PostgreSQL ACID guarantees, anti-theft bindings, and Cloudflare deployment.


---

# 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://h00dr00st.gitbook.io/h00d-r00st-1/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.