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

# Token Data 

| Attribute                     | Detail                                                                                                                                                                                    |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Token Ticker                  | PROPC                                                                                                                                                                                     |
| Total Supply (Fixed)          | 100,000,000 $PROPC                                                                                                                                                                        |
| Token Type                    | ERC-20 (Ethereum)                                                                                                                                                                         |
| Inflation                     | None - Fixed supply,  no new tokens will be minted                                                                                                                                        |
| Initial Burn                  | 36,236,663.00  $PROPC                                                                                                                                                                     |
| Circulating Supply Management | Circulating supply adjustments are managed through ecosystem usage, operational token utilization, and community-based governance engagement.                                             |
| Primary Demand Drivers        | <ol><li>Operational ecosystem usage (technology service fees)</li><li>On-chain utility and ecosystem participation</li><li>Operational token utilization for ecosystem services</li></ol> |
| Settlement Model              | All internal technology fees (Prop.com -> Propchain) settled in $PROPC                                                                                                                    |
| Secondary Market Liquidity    | Tokens available on DEXs/CEXs to enable user access and inistutional entry points                                                                                                         |

**Contract Address:** 0x9ff58067Bd8D239000010c154C6983A325Df138E&#x20;

**CMC:** <https://coinmarketcap.com/currencies/propchain/>

**Dune**: <https://dune.com/propchain/propcom-ecosystem/e68322c5-9a20-4725-a48c-14984bce5127>\
\
**Important Clarification:**\
The $PROPC token serves strictly as a utility token for accessing ecosystem services and platform technologies. It does not provide financial returns, passive income, or profit distributions. Circulating supply adjustments and token demand mechanisms described here are exclusively related to operational utility and ecosystem participation, explicitly excluding investment-related benefits.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.propchain.com/propchain-foundation/usdpropc-utility-token/token-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.