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

# Dawn Labs

**Your Solana Yield Partner**

Dawn Labs is a **Solana operations partner** for exchanges, DATs (Digital Asset Treasury), lending protocols, traditional finance firms, and high-net-worth individuals. We combine deep validator infrastructure expertise with staking yield optimization to deliver institutional-grade returns.

## Services

### Yield Strategies

| Service                                                     | Description                                                                       | Status |
| ----------------------------------------------------------- | --------------------------------------------------------------------------------- | ------ |
| [**SOL Staking**](/about-dawn-labs/services.md#sol-staking) | Native Staking, LST Staking, Multiple Staking (0% commission + kickback for VIPs) | Live   |

### Consulting

| Service                                                               | Description                                                         | Status    |
| --------------------------------------------------------------------- | ------------------------------------------------------------------- | --------- |
| [**Validator Growth**](/about-dawn-labs/services.md#validator-growth) | Onboarding, training, and growth strategy for enterprise validators | Available |

## Why Dawn Labs?

* **Validator-Native** — Our yield strategies start at the infrastructure layer, giving us structural alpha unavailable to pure DeFi aggregators
* **$150M+ Assets Managed** — Proven track record with institutional-scale operations
* **APAC-Based** — Bridging the Japanese market to the Solana ecosystem
* **Compliance-Ready** — Navigate regulation and audit requirements together

## Company Profile

|                  |                                                   |
| ---------------- | ------------------------------------------------- |
| **Legal Entity** | CHAIN TEC LAB - FZCO                              |
| **Location**     | IFZA Business Park, DDP, Dubai Silicon Oasis, UAE |
| **Website**      | [dawnlabs.tech](https://dawnlabs.tech)            |
| **X (Twitter)**  | [@dawnlabs00](https://x.com/dawnlabs00)           |

## Team

| Name               | Role | Contact                                         |
| ------------------ | ---- | ----------------------------------------------- |
| **Yutaro Nagumo**  | CEO  | [@SouthCloud0703](https://x.com/SouthCloud0703) |
| **Toshiyuki Tega** | CTO  | [@SoftgateJa](https://x.com/SoftgateJa)         |

***

> **Disclaimer**: Staking and leveraged staking strategies involve risk. Past performance does not guarantee future results. Please review our [Disclaimer](/legal/disclaimer.md) before using our services.


---

# 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.dawnlabs.tech/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.