> 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/migration-history.md).

# Migration history

The project was previously called **Defidash**. It became **Polydash**, and the token moved from Base to Robinhood Chain. This page records the official contract addresses in order, so holders and data providers can match them.

## Contracts, old to current

| Label                                              | Chain           | Contract                                     | Decimals | Total supply    |
| -------------------------------------------------- | --------------- | -------------------------------------------- | -------- | --------------- |
| Defidash (old)                                     | Base            | `0xd6df108d516a5dc83f39020a349085c79d4edf0d` | 9        | 20,000,000      |
| Polydash on Base (old)                             | Base            | `0xbec5ade968d368bd65a42a7667b178c929e75c59` | 18       | 100,000,000,000 |
| **Polydash on Robinhood Chain (current official)** | Robinhood Chain | `0x319525528f42167ef7fc18b77b889958080568e4` | 18       | 100,000,000,000 |

The official token's on-chain `symbol()` is `polydash` (all lowercase). This documentation uses $POLYDASH as the ticker in prose.

## How holders were moved

* **Method.** A snapshot of holders, then an airdrop. There was no swap portal.
* **Ratio.** One-to-one by **percentage of supply** for all holders.
* **Token count for the Defidash to Polydash step.** 5,000 POLYDASH for each 1 DEFIDASH, which takes 20,000,000 to 100,000,000,000.
* **Base to Robinhood Chain.** The 100,000,000,000 supply stayed the same.

{% hint style="info" %}
The move is one-to-one by share of supply, not by raw token count. Data providers that define a "1:1 migration" as an equal token count and an equal supply treat this as a different case, so a provider may create a new page rather than update the old one.
{% endhint %}

## Official announcements

The migration was announced from [@Polydash\_](https://x.com/Polydash_), including a thread about the move to Robinhood Chain, with earlier posts for the rebrand and the airdrop. Only the Robinhood Chain contract is the official token.

## Data providers

The old Defidash page on CoinGecko has been removed. A request to list Polydash has been submitted. This documentation does not claim a listing is live.

## What to check

* The official address is `0x319525528f42167ef7fc18b77b889958080568e4` on Robinhood Chain.
* Do not buy or send tokens at the older Base addresses expecting them to be current.
* There was no swap portal. Treat any link in a direct message that offers to swap or claim old tokens as suspicious.


---

# 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/migration-history.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.
