# Overview

Taker is the Bitcoin incentive layer, leveraging multiple reward frameworks to nudge millions of users to adopt, hold and apply Bitcoin and its derivatives, scaling yields and expanding the Bitcoin community by 100x. Taker is not a traditional L2 or a purely financial protocol; rather, it is oriented towards traffic and user growth, targeting a broad range of Bitcoin holders to establish a Bitcoin Holder growth engine. It is comprehensively ahead of competitors in terms of user base, activity levels, investment institutions, and product implementation, making it a project with significant growth potential in the Bitcoin ecosystem. For exchanges, Taker can not only bring transaction volume and on-chain asset accumulation but also help platforms reach the underserved market of retail Bitcoin users, providing unique commercial value.<br>

**Key Features:**

1. Bitcoin retail user-oriented

* Taker targets Bitcoin retail users and potential Bitcoin holders and users;
* Taker lite-mining and sowing provide zero-capital requirements for retail users and potential users to join the Bitcoin ecosystem;-Taker aims to increase the on-chain Bitcoin holders and users community and hence can generate real native yields for users.<br>

2. EVM-Compatible Layer 1

* $TAKER serves as the native gas token-
* Native AMM DEX integration similar to Uniswap V3
* Taker lend supports Bitcoin LSD/LRTs<br>

3. Long-term sustainability

* veTokenomics and Long-term stakeholder alignment- Long-term growth model:&#x20;
* Task-driven user acquisition → Lend/Swap solid but rigid-demand applications → User conversion and retention


---

# 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.taker.xyz/taker/taker-protocol/taker-chain/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.