# Verification On-chain

## Five Facts to Verify

| Fact         | Question                                |
| ------------ | --------------------------------------- |
| Contract     | Does PRO actually exist on-chain?       |
| Minting      | Is minting tied to treasury collateral? |
| Treasury     | Are the assets real?                    |
| Liquidity    | Is LP established and locked?           |
| Transparency | Is data synced to third parties?        |

## Contract Addresses

{% tabs %}
{% tab title="PRO Token" %}

```
0x8d65744527f55d0b2338350912d5c99a81ddf0e2
```

[View on BscScan →](https://bscscan.com/token/0x8d65744527f55d0b2338350912d5c99a81ddf0e2)

Verify: Token name, transaction history, holder list.
{% endtab %}

{% tab title="Treasury" %}

```
0xf9074b5C035c961443373F78A6344e5Adc61d314
```

[View on BscScan →](https://bscscan.com/address/0xf9074b5C035c961443373F78A6344e5Adc61d314)

Verify: USDT balance, PRO balance, inflows/outflows.
{% endtab %}

{% tab title="Execution Contract" %}

```
0xc2D8595Fe8D904a8665059D68A6fa2467dF09A13
```

[View on BscScan →](https://bscscan.com/address/0xc2D8595Fe8D904a8665059D68A6fa2467dF09A13)

Functions: Collateral minting, LP establishment, PRO purchase.

This is the **only buy entry** — no private channels, no multiple price points.
{% endtab %}

{% tab title="Permission Custody" %}

```
0xE561346bAbE61050F04B6756c303c1C9777e4a59
```

[View on BscScan →](https://bscscan.com/address/0xE561346bAbE61050F04B6756c303c1C9777e4a59)

Current permission holder. Post-launch, transfers to community multi-sig (top 20 global performers).
{% endtab %}
{% endtabs %}

## Key Transactions

{% tabs %}
{% tab title="Minting Example" %}

```
0x6e98755f8a7fb27c8e67082add593e7d36118df8d5994f7b634323651d833683
```

[View Transaction →](https://bscscan.com/tx/0x6e98755f8a7fb27c8e67082add593e7d36118df8d5994f7b634323651d833683)

* Source: `0x000…000` (mint event, not transfer)
* Amount: 200,000 PRO
* Destination: Treasury contract

Minting only happens when collateral enters. No exceptions.
{% endtab %}

{% tab title="LP Thickening" %}

```
0x0cd5b2d6bb931bfdcd2e67c4a1f6dba9e097b5aca4a752391497ea9dfa83f4d8
```

[View Transaction →](https://bscscan.com/tx/0x0cd5b2d6bb931bfdcd2e67c4a1f6dba9e097b5aca4a752391497ea9dfa83f4d8)

* 800,000 USDT applied
* Paired with PRO
* LP pool thickened

This isn't announced — it's executed.
{% endtab %}
{% endtabs %}

## Third-Party Verification

Data is independently pulled by external platforms:

**Ave.ai:** [View PRO →](https://m.ave.ai/token/0x8d65744527f55d0b2338350912d5c99a81ddf0e2-bsc)

* Token info
* Real-time price
* Liquidity data
* Transaction activity

Not just on official pages — third parties display it too.

## Summary

| Fact                  | How to Verify                                                                     |
| --------------------- | --------------------------------------------------------------------------------- |
| Contract exists       | Check PRO address on BscScan                                                      |
| Minting follows rules | Review mint transactions — source is always `0x000…000` with treasury destination |
| Treasury is real      | Check treasury address balances                                                   |
| LP is locked          | Review LP thickening transaction                                                  |
| Data is public        | Cross-check on Ave.ai                                                             |

> Transparency isn't a slogan. It's a verifiable result.

When verification is in your hands, trust doesn't need to be asked for.

## Related

* [Minting Model](broken://pages/7fb8ec28cfefa45740504db60c29f8fbda3aa5fd)
* [Architecture](broken://pages/2749b8c2d7d9d2bfd6581cde3756ab21d0f74f98)


---

# 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:

```
GET https://cryptodao-it.gitbook.io/c-dao/3.-technical/verification-on-chain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.