> 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/polydash-token.md).

# $POLYDASH token

The official $POLYDASH token on Robinhood Chain. Contract address, supply, and what it is used for.

{% hint style="success" %}
**Official $POLYDASH contract**

Network: **Robinhood Chain** (chain ID 4663)

Address: `0x319525528f42167ef7fc18b77b889958080568e4`

[View on Blockscout](https://robinhoodchain.blockscout.com/token/0x319525528f42167eF7fC18b77b889958080568e4) · [Sourcify](https://repo.sourcify.dev/4663/0x319525528f42167eF7fC18b77b889958080568e4) · [GeckoTerminal pool](https://www.geckoterminal.com/robinhood/pools/0xc37d18932ac3bf4d8482ae1b210bbc640a367e708fedda95cfa6724f685274b5)
{% endhint %}

This is the only official $POLYDASH token. Older Base contracts from earlier versions of the project are not the current token. See [Migration history](https://polydash.gitbook.io/polydash-docs/polydash-token/migration-history.md). Always check the address against this page before you trade.

## Token details

Read from the contract on Robinhood Chain on November 14, 2026.

| Item            | Value                                                                                                                                                               |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name            | Polydash                                                                                                                                                            |
| Symbol on-chain | `polydash` (all lowercase). The ERC-20 `symbol()` value is `polydash`. This documentation uses $POLYDASH as the ticker in prose                                     |
| Decimals        | 18                                                                                                                                                                  |
| Total supply    | 100,000,000,000 (100B)                                                                                                                                              |
| Deployment      | A standard Clanker deployment on Robinhood Chain. The token contract is not in the Polydash repository                                                              |
| Sourcify        | Match (creation and runtime), recorded October 28, 2026                                                                                                             |
| Trading pool    | POLYDASH/WETH on Uniswap V4, pool id `0xc37d18932ac3bf4d8482ae1b210bbc640a367e708fedda95cfa6724f685274b5`                                                           |
| Token list      | [polydash.tokenlist.json](https://raw.githubusercontent.com/polydash-labs/Polydash/main/tokenlist/polydash.tokenlist.json), a Uniswap-schema list in the repository |

## What the token is used for

The Polydash site describes these areas of use. They are stated plans and features, not promises, and they can change as products launch.

| Area                                                             | Status in this documentation                                                                                                                                             |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Staking                                                          | A POLYDASH rewards pool is deployed. See [Buybacks and rewards pool](https://polydash.gitbook.io/polydash-docs/polydash-token/buybacks-and-rewards-pool.md)              |
| Buybacks and burns                                               | A capped buyback vault is deployed. Both launch factories send 40% of collected platform fees to it. The vault has not received fees or run a buy yet. See the same page |
| Governance                                                       | Listed on dasheco.xyz as planned utility. A DAO page exists on dasheco.xyz                                                                                               |
| Access, premium features, product discounts, trading fee rewards | Listed on dasheco.xyz as planned utility                                                                                                                                 |

## How platform fees are routed on-chain

Both Polypad launch factories were read on November 14, 2026 with this configuration:

| Setting           | Live value                                                                                                                                                    |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `buybackEnabled`  | true, on the current factory and the earlier factory                                                                                                          |
| `buybackBps`      | 4,000 (**40%** of collected platform fees) to the buyback vault                                                                                               |
| Remainder         | **60%** to the platform fee wallet `0x9a21c75aC263cC43125E70200636f6397f8776d0`                                                                               |
| `buybackContract` | PolydashBuybackVault [`0x35Ad6AC64fb53ED7154b6e6E0Ef84C6E12d7B193`](https://robinhoodchain.blockscout.com/address/0x35Ad6AC64fb53ED7154b6e6E0Ef84C6E12d7B193) |

When the vault runs a buy, **62.5%** of the POLYDASH bought is burned and **37.5%** is held for stakers. If a buy runs, that is **25%** of platform fees burned and **15%** held for stakers. See [Buybacks and rewards pool](https://polydash.gitbook.io/polydash-docs/polydash-token/buybacks-and-rewards-pool.md).

Creator fees are separate. They are 0% to 5%, set at launch, and go to the creator's payout wallet. They are not part of this split.

### Whitepaper target on dasheco.xyz

dasheco.xyz shows a **target allocation of protocol fees from the whitepaper**: buybacks and burns 40%, holder and staker rewards 30%, product development and operations 20%, and treasury and liquidity 10%. Those 40/30/20/10 figures are not what the live fee contracts route. The 30/20/10 legs have no on-chain splitter. NFT and staking platform-fee shares are also not split in the contracts; the Polypad buybacks page states that 40% of those fees is sent to the vault manually.

## Listings and data trackers

As of November 14, 2026, listing requests with data trackers are in progress, and this page does not claim that any listing is live. POLYDASH trades on a Uniswap V4 pool on Robinhood Chain and appears on GeckoTerminal.

## Official links

* X: [@Polydash\_](https://x.com/Polydash_)
* Telegram: [t.me/polydashofficial](https://t.me/polydashofficial)
* Website: [dasheco.xyz](https://dasheco.xyz)

## Risks

Tokens can lose value, including all of it. Nothing here is a promise of price, returns, buybacks, or rewards. Phishing copies of the token exist across crypto. Verify the contract address on this page.


---

# 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/polydash-token.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.
