# Overview

<figure><img src="https://1334354907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK1WFnyW0GzxjPAF9IaSq%2Fuploads%2F2ns3NoUDXYELQpwDTzp8%2FIntroducing%20Henjin%20the%20Taiko%20DEX.png?alt=media&#x26;token=aca51d1b-437f-4517-887c-91abcc73d516" alt=""><figcaption></figcaption></figure>

[**Henjin**](https://henjin.xyz) is an ecosystem-focused, community-driven DEX and Launchpad built on [**Taiko**](https://taiko.xyz) **and** [**Base**](https://www.base.org/).

Henjin has been built as a highly efficient and customizable protocol, allowing both builders and users to leverage our custom infrastructure for deep, sustainable, and adaptable liquidity. Henjin moves beyond the traditional design of DEXs to focus on offering a tailored approach that prioritises composability.

### Core values & goals

* To provide the Taiko and Base ecosystem with a wide range of innovative features, enabling them to have an extremely high degree of flexibility and control over their own liquidity
* To support new protocols launching on Taiko and Base, providing the tools that enable them to launch, bootstrap liquidity, and sustain their growth
* To make available to all permissionless tools allowing projects of all sizes to leverage our protocol in whatever way suits their needs
* To deliver state-of-the-art functionality that can be easily integrated, built upon, and leveraged by other protocols within the ecosystem
* To apply the real yield narrative to a DEX and liquidity providing - creating innovative emissions strategies that leverage more sustainable tokenomics, aligning incentives with builders, users, and the protocol &#x20;
* To be as decentralized as possible, allowing the community to drive the protocol forward as a DAO, whilst enabling the core team to sustainably build the protocol


---

# 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.henjin.xyz/overview.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.