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

# Welcome to Polydash

Polydash is a product-driven onchain ecosystem on Robinhood Chain. This is the official documentation.

**Polydash builds onchain products for Robinhood Chain.** Its main product, **Polypad**, lets anyone launch a token, an NFT collection, or a tokenized fund in a few minutes, with rules that live in public smart contracts instead of in a company's back office.

Every product follows the same principles:

* **Non-custodial.** You sign every transaction in your own wallet. Polydash never holds your keys.
* **Rules in code.** Fees, limits, and time locks are written into verified contracts. Where a team can change a setting, these docs say what the setting is and what it cannot touch.
* **Open source.** Contracts, agents, and the web app are published at [github.com/polydash-labs/Polydash](https://github.com/polydash-labs/Polydash). Contract source is verified on Sourcify.
* **Plain risk labels.** The contracts are **Not audited.** An outside review is planned. Read [Security overview](https://polydash.gitbook.io/polydash-docs/security-and-risk.md) before you use anything.

{% hint style="info" %}
**Official $POLYDASH token**

Network: Robinhood Chain (chain ID 4663)\
Contract: [`0x319525528f42167ef7fc18b77b889958080568e4`](https://robinhoodchain.blockscout.com/token/0x319525528f42167eF7fC18b77b889958080568e4)\
Supply: 100,000,000,000 (100B), 18 decimals

This is the only official $POLYDASH contract. Older Base contracts exist from earlier versions of the project. See [Token overview](https://polydash.gitbook.io/polydash-docs/polydash-token.md) and [Migration history](https://polydash.gitbook.io/polydash-docs/polydash-token/migration-history.md).
{% endhint %}

## What you can do with Polydash

{% columns %}
{% column %}

### Launch

Create a fixed-supply token with a bonding curve, an optional commitment window, and automatic graduation into a Uniswap V4 pool with permanently locked liquidity.

[Polypad launchpad →](https://polydash.gitbook.io/polydash-docs/polypad.md)
{% endcolumn %}

{% column %}

### Stake

Create or join permissionless reward pools for any token, or stake NFTs for token rewards over a fixed window.

[Staking pools →](https://polydash.gitbook.io/polydash-docs/polypad/staking-pools.md)
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

### Invest through funds

Tokenized funds sell equal ERC-721 shares for ETH. Rules are fixed when the fund is created, and holders can exit through the contract.

[Polypad Funds →](https://polydash.gitbook.io/polydash-docs/polypad-funds.md)
{% endcolumn %}

{% column %}

### Build with agents

AI agents and scripts can prepare launches through a non-custodial API and an MCP server. The agent never sees a private key.

[Agent launch API →](https://polydash.gitbook.io/polydash-docs/agents-and-api/agent-launch-api.md)
{% endcolumn %}
{% endcolumns %}

## Start here

| If you want to...                   | Read                                                                                                  |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Connect a wallet to Robinhood Chain | [Wallet and network](https://polydash.gitbook.io/polydash-docs/getting-started/wallet-and-network.md) |
| Move ETH onto Robinhood Chain       | [Bridging ETH](https://polydash.gitbook.io/polydash-docs/getting-started/bridging.md)                 |
| Launch a token                      | [Launch a token](https://polydash.gitbook.io/polydash-docs/polypad/launch-a-token.md)                 |
| Understand fees                     | [Fees](https://polydash.gitbook.io/polydash-docs/polypad/fees.md)                                     |
| Look up a contract address          | [Contract registry](https://polydash.gitbook.io/polydash-docs/smart-contracts.md)                     |
| Understand the risks                | [Risk disclosure](https://polydash.gitbook.io/polydash-docs/security-and-risk/risk-disclosure.md)     |
| Build an integration                | [Agent launch API](https://polydash.gitbook.io/polydash-docs/agents-and-api/agent-launch-api.md)      |

## Official links

* Polypad: [polypad.family](https://polypad.family)
* Company site: [dasheco.xyz](https://dasheco.xyz)
* X: [@Polydash\_](https://x.com/Polydash_)
* Telegram: [t.me/polydashofficial](https://t.me/polydashofficial)
* GitHub: [polydash-labs/Polydash](https://github.com/polydash-labs/Polydash)

{% hint style="warning" %}
Using these contracts can result in loss of funds. Only use money you can afford to lose. Nothing in this documentation is a promise of returns, liquidity, or future value.
{% 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://polydash.gitbook.io/polydash-docs/welcome.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.
