> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/resources/contract-addresses.md).

# Contract Addresses

## Mainnet Contracts (Polygon)

| Contract             | Address             | Verified |
| -------------------- | ------------------- | -------- |
| **TPT Token**        | `[To be published]` | —        |
| **Staking**          | `[To be published]` | —        |
| **Escrow**           | `[To be published]` | —        |
| **Invoice Registry** | `[To be published]` | —        |
| **Settlement**       | `[To be published]` | —        |

{% hint style="warning" %}
Contract addresses will be published upon mainnet deployment. Always verify addresses through official channels before interacting.
{% endhint %}

***

## Testnet Contracts (Polygon Mumbai/Amoy)

| Contract      | Address             | Status |
| ------------- | ------------------- | ------ |
| **TPT Token** | `[To be published]` | —      |
| **Staking**   | `[To be published]` | —      |
| **Escrow**    | `[To be published]` | —      |

***

## Verification

All contracts are verified on Polygonscan:

* [TPT Token](#) — \[Link to be added]
* [Staking](#) — \[Link to be added]
* [Escrow](#) — \[Link to be added]

***

## Security

### How to Verify Official Contracts

{% stepper %}
{% step %}

### Check this documentation page

Ensure the contract address is listed on this official documentation page.
{% endstep %}

{% step %}

### Verify on official social channels

Confirm addresses via the project's official social channels (Twitter, Discord).
{% endstep %}

{% step %}

### Confirm on Polygonscan verification

Check the contract's verification status on Polygonscan.
{% endstep %}

{% step %}

### Cross-reference with team announcements

Confirm addresses match those announced by the team through official channels.
{% endstep %}
{% endstepper %}

### Red Flags

* Contracts shared via DMs
* Addresses not listed here
* Requests to interact with unverified contracts
* Urgency or pressure to act quickly

{% hint style="danger" %}
**Never interact with unverified contracts.** Scammers may create fake contracts. Always verify through official sources.
{% endhint %}

***

## Multi-sig Addresses

| Purpose               | Address             | Signers |
| --------------------- | ------------------- | ------- |
| **Treasury**          | `[To be published]` | 3-of-5  |
| **Upgrade Authority** | `[To be published]` | 3-of-5  |
| **Emergency**         | `[To be published]` | 2-of-5  |

***

## Integration

For developers integrating with TPT Protocol:

{% code title="integration.js" %}

```javascript
// Example: TPT Token Address (Polygon Mainnet)
const TPT_TOKEN = "[To be published]";

// Example: Staking Contract
const STAKING = "[To be published]";
```

{% endcode %}

Full integration documentation will be available in the Developer Guide.


---

# 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://triple-plus-global.gitbook.io/tpt-whitepaper/resources/contract-addresses.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.