> 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/brand-kit.md).

# Brand kit

Names, boilerplate, logos, colors, and type for press, trackers, and builders.

This page follows the [Polypad brand kit](https://polypad.family/brand). Use it when you write about Polydash or Polypad.

## Names

| Name      | Use                                                       |
| --------- | --------------------------------------------------------- |
| Polydash  | The company                                               |
| Polypad   | The launchpad at [polypad.family](https://polypad.family) |
| $POLYDASH | The token ticker only                                     |

Write "Polydash", not "POLYDASH" or "polydash", when you mean the company. Write "Robinhood Chain" in full.

## Boilerplate

**Short.** Polypad is a non-custodial token launchpad on Robinhood Chain, built by Polydash.

**Long.** Polypad lets anyone launch a token on a bonding curve, trade it, and move it to a Uniswap V4 pool with locked liquidity once it graduates. It also supports NFT collections, staking pools, and AI agents that help review tokens. Polypad is built by Polydash.

## Logo

The Polydash mark is a 3D tile pattern. It is shown here as white on black.

Download the full kit, with white, dark, and green marks, a 256 px logo, and a 1360 x 430 banner, from [polypad.family/brand](https://polypad.family/brand). Leave clear space around the mark equal to at least a quarter of its width.

## Colors

These are the colors used on polypad.family. This documentation uses black and white only.

| Name                   | Hex       |
| ---------------------- | --------- |
| Polypad Green (accent) | `#00E676` |
| Background             | `#0A0A0A` |
| Card                   | `#121212` |
| Muted surface          | `#1A1A1A` |
| Border                 | `#262626` |
| Muted text             | `#8C8C8C` |
| Text                   | `#FFFFFF` |

## Typography

* **Inter** for headings and body.
* **JetBrains Mono** for addresses, numbers, and code.

## Token reference

$POLYDASH on Robinhood Chain (chain ID 4663): `0x319525528f42167eF7fC18b77b889958080568e4`. See the [$POLYDASH token](https://polydash.gitbook.io/polydash-docs/polydash-token.md) page.

## Do not

* Do not imply a partnership, review, or endorsement that does not exist.
* Do not describe the contracts as reviewed. They are **Not audited.**
* Do not quote returns or price targets for any Polydash product.


---

# 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/brand-kit.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.
