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

# $KUDO

$KUDO token details, supply and the official contract.

|              |                                                                                                                                             |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Token        | $KUDO                                                                                                                                       |
| Chain        | Robinhood Chain                                                                                                                             |
| Launched     | October 2026, via the Pons Family launchpad                                                                                                 |
| Contract     | `0x80877Fe12eDE96F807422D5D4Ee4f4c47cebC8Ff`                                                                                                |
| Total supply | 1,000,000,000                                                                                                                               |
| Explorer     | [Robinhood Chain Etherscan](https://robin.etherscan.io/token/0x80877Fe12eDE96F807422D5D4Ee4f4c47cebC8Ff)                                    |
| Trading      | Uniswap V4, KUDO/USDG ([DexScreener](https://dexscreener.com/robinhood/0x26dd43b1be6b08ee36562e6c3ed807bb4b6f526f12413a693c788116e151eeb6)) |

{% hint style="warning" %}
This is the only official $KUDO contract. Kudo never sends contract addresses by DM. See [Official links & safety](/links.md).
{% endhint %}

## Supply removed

200,000,000 $KUDO (20% of supply) was sent from the team wallet to the Pons launch locker, a verified contract with no withdraw or unlock function. Those tokens are effectively burned.

* [View the transaction](https://robin.etherscan.io/tx/0x1bc7501216a458732ef514ce24bb2db279e7d782b58038713e431cdf00edc452)
* [View the locker contract](https://robin.etherscan.io/address/0x267444D099b10fB5Ed7c3Cc7B7c767AdcA574952)

On an explorer the locker shows 281.6M $KUDO: Kudo's 200M plus 81.6M from the Pons Family launch lock. Total supply stays at 1,000,000,000.

## Utility

$KUDO is planned to secure open Evaluators. Independent Evaluators will stake $KUDO to settle promises and will be subject to slashing. This arrives in the final phase of the [roadmap](/roadmap.md) and is not live yet.


---

# 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.kudo.archi/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.