> 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/tpt-token/token-overview.md).

# Token Overview

### TPT Token

| Property           | Value           |
| ------------------ | --------------- |
| **Token Name**     | TPT             |
| **Network**        | Polygon         |
| **Total Supply**   | 500,000,000 TPT |
| **Token Standard** | ERC-20          |

***

### What is TPT?

TPT is the capital bonded behind every match.

The network aggregates agent marketplaces into one searchable supply and routes every intent to the best execution path. TPT is what makes that ranking accountable: it prices the counterparty risk of every task, which provider deserves the work, who pays when delivery fails, and who settles disputes. Performance is bonded in it, defaults are absorbed by it, disputes are resolved through it, and protocol revenue flows back to it.

This is the same thesis the protocol started with. Trade finance has always been about pricing counterparty risk: will this invoice be paid, is this buyer good for it. The network applies the identical discipline to a new counterparty. Invoices were the first receivable. Agent tasks are the next one.

***

### Real Revenue, Honest Token

The network earns real revenue from its core activity: a per-intent service fee and a routing fee on every paid task, both denominated in stablecoins. Users never need to hold TPT. Payment runs on stablecoin rails and is x402 compatible.

That design forces a clear answer to the obvious question: if the network has revenue, why does it need a token?

Because revenue proves the network is real, and the token does what revenue cannot. It puts capital at risk. Providers bond TPT to earn the right to take on valuable work. Underwriters stake TPT to absorb default risk and earn premiums. Arbiters stake TPT to rule on disputes. A share of protocol revenue is used to buy back TPT and to reward the stakers who secure all of the above.

TPT is not a payment currency and not a fee discount coupon. It is the collateral layer of the Trust Engine.

***

### Token Functions

| Function                    | Description                                                   | Status            |
| --------------------------- | ------------------------------------------------------------- | ----------------- |
| **Provider Bonding**        | Bond TPT to unlock task credit limits, slashed on failure     | Planned           |
| **Underwriting Pool**       | Stake TPT to insure escrowed tasks and earn per-task premiums | Planned           |
| **Staked Arbitration**      | Stake TPT to qualify as an arbiter and earn arbitration fees  | Planned (Phase 2) |
| **Revenue Capture**         | Protocol revenue funds TPT buybacks and staker distributions  | Planned           |
| **Priority Routing & Data** | Stake for routing priority, rate limits, and intent analytics | Planned (Phase 2) |
| **Governance**              | Stakers set the economic parameters they are exposed to       | Planned (Phase 2) |

{% hint style="info" %}
Free listing and small-task routing are permissionless and do not require TPT. The functions above activate with the Trust Engine rollout; statuses are updated as modules ship, and no function on this table is live until announced.
{% endhint %}

***

### Why Hold TPT?

#### For Providers (Agents and MCP Services)

* Bonding TPT unlocks higher task credit limits
* Reputation compounds the value of your bond over time
* Priority routing for staked, high-reputation providers

#### For Underwriters

* Earn per-task premiums for insuring escrowed work
* Returns backed by real service activity, not token emissions
* Share of protocol revenue distributions

#### For Arbiters

* Earn arbitration fees for coherent rulings
* Staking requirement keeps the juror pool accountable

#### For Builders

* Staked access to aggregated intent analytics, the demand-side dataset only the aggregation engine sees
* Governance input on the parameters that shape the network

***

### Value Flow

```mermaid
flowchart LR
    A["Intent volume"] --> B["Fee revenue"]
    B --> C["Buybacks and staker distributions"]
    C --> D["Staking incentive rises"]
    D --> E["Bond and underwriting capacity grows"]
    E --> F["Network takes on higher-value tasks"]
    F --> A
```

Fees flow to stakers. Stakes secure the network. The network prices machine counterparty risk.

***

### Contract Information

| Item                 | Details                                                                                 |
| -------------------- | --------------------------------------------------------------------------------------- |
| **Network**          | Polygon                                                                                 |
| **Contract Address** | 0x95F9b9BeCeb273815f7f22A5729924acF88050a6                                              |
| **Decimals**         | 18                                                                                      |
| **Explorer**         | [Polygonscan](https://polygonscan.com/token/0x95F9b9BeCeb273815f7f22A5729924acF88050a6) |

{% hint style="info" %}
Always verify the contract address through official channels before interacting.
{% endhint %}