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

# V4 token

V4 is Programmable's token on Robinhood Chain. It was created with one billion tokens and has no further minting. Identify it by its contract address.

| Detail          | Value                                                                                                                                  |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Name and ticker | Programmable, V4                                                                                                                       |
| Network         | Robinhood Chain, chain ID `4663`                                                                                                       |
| Contract        | [`0xC60bA256B44334A0Cd2C7242E98B88f031abB006`](https://robinhoodchain.blockscout.com/token/0xC60bA256B44334A0Cd2C7242E98B88f031abB006) |
| Initial supply  | 1,000,000,000 V4                                                                                                                       |

## Liquidity and trading fees

The V4/ETH pool charges a **1% trading fee**, shared by liquidity providers according to their positions. Wallet-to-wallet transfers do not incur this pool fee.

Programmable's liquidity is held in a [locked position](https://robinhoodchain.blockscout.com/address/0x9f9424BbCCe8a865f70155fe40Fb22A103eBEc63), NFT `1708785`. The position can collect fees while its liquidity remains locked. It earns ETH on buys and V4 on sells.

## Buybacks and burns

Programmable allocates **80% of its collected fee revenue** to manual V4 buybacks and burns. The remaining 20% goes to its treasury and operating costs. This includes collected platform fees and quote-asset fees from its own liquidity position; creator fees and module rewards are excluded. There is no automatic buyback on each trade or fixed daily schedule. [Fees and revenue](/docs/launch/economics.md#platform-revenue) explains the collection basis and tracked wallets.

V4 collected directly from Programmable's own liquidity fees is also burned. It is recorded separately from V4 bought with fee revenue.

The project's burn wallet is `0x39544A7023081B56D7405c1af0bFaf72da7e24F6`. Burns send V4 to `0x000000000000000000000000000000000000dEaD`. These tokens are excluded from circulation, while the contract's reported total supply remains one billion. The [Dune dashboard](https://dune.com/programmablehq/analytics) links recorded burns to their transactions and distinguishes project burns from burns by other holders.

V4 does not give holders company ownership or a right to platform revenue. Buybacks and burns do not guarantee a price or return. This token is separate from Programmable's earlier Ethereum tokens.


---

# 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://programmable.market/docs/launch/v4-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.
