# Introduction

DEDCAT is a suite of Hyperliquid-native dApps that route 100% of net protocol revenue to $DEDCAT stakers, paid in $HYPE.<br>

> DEDCAT exists to route protocol revenue to the people who participate in the system, rather than to passive intermediaries.&#x20;

### How Value Flows

* Every DEDCAT dApp continuously routes its revenue to stakers, paid as yield in $HYPE
* Yield is earned passively, but to claim it you must participate in DedcatBounce (Active Staking)
* Participation generates revenue, revenue creates yield, claiming that yield requires participation
* The loop reinforces itself

### DedcatBounce

DedcatBounce is the first dApp built into the DEDCAT system.

It serves as the primary participation layer and establishes the active loop that connects usage, staking, and yield. Future dApps integrate into the same revenue and staking structure.

### How to Participate

At launch, participation in DEDCAT begins with DedcatBounce.

DedcatBounce establishes the participation loop that underpins the system. As Purrps, Truthbomb and additional dApps integrate into DEDCAT, they will route all revenue to stakers and reinforce this loop.

## <mark style="color:$primary;">**WELCOME TO DEDCAT**</mark>

<figure><img src="https://1382820398-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2mR0Ji47mO1JJnWdKzi7%2Fuploads%2FdSIL6ciHvGK89jt0S8KG%2Feuphoria%20draft.jpg?alt=media&#x26;token=2e124aa0-bc12-4bef-b7f7-143df2c9838a" alt=""><figcaption></figcaption></figure>


---

# 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://dedcat.gitbook.io/dedcat-docs/welcome-to-dedcat/introduction.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.