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

# Introduction

**Dynamic Hooks is the programmable market layer on Robinhood Chain.**

Launch a market. Program its economics. Let it evolve on-chain.

Every launchpad so far asks you to set the rules once, at launch, and live with them. A fee is a number. A fee recipient is an address. Liquidity is locked or it isn't. Nothing changes after the first block, no matter what happens to the market or the people behind it.

Dynamic Hooks is built on a different premise: **a market's rules should respond to what the market does and to what can be proven about it.** A creator verifies their identity, and fee routing changes. Liquidity crosses a threshold, and the fee drops. A milestone is attested, and rewards switch on. An agent proves a condition, and a predefined rule fires. All of it inside the swap, enforced by a Uniswap v4 hook, with hard limits that no rule can cross.

This document explains what a market is here, how its program works, who gets paid, what can and cannot change, and what the $DHOOKS token does. It has no dates in it. Things ship in an order, and each step is announced when it is done.

{% hint style="info" %}
If you read one page, read [Programs and rules](https://docs.dynamichooks.com/programs-and-rules.md). If you are deciding whether to hold $DHOOKS, read [Straight talk](https://docs.dynamichooks.com/straight-talk.md) first.
{% endhint %}


---

# 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://docs.dynamichooks.com/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.
