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

# Contract Addresses

Official ASK Token Contracts

ASK is an omnichain token deployed using the LayerZero OFT (Omnichain Fungible Token) standard.&#x20;

The smart contract addresses listed below represent the only official ASK token contracts authorized by Permission.

#### ✅ ASK Contract Addresses

<table><thead><tr><th width="158.59161376953125">Network</th><th width="160.5440673828125">Token Standard</th><th width="432.571044921875">Contract Address</th></tr></thead><tbody><tr><td><strong>Base</strong></td><td>OFT-20</td><td><code>0xBB146326778227A8498b105a18f84E0987A684b4</code></td></tr><tr><td><strong>Polygon</strong></td><td>OFT-20</td><td><code>0xaA3717090CDDc9B227e49d0D84A28aC0a996e6Ff</code></td></tr></tbody></table>

### 🔗 Stargate Support

ASK is officially integrated into [Stargate](https://layerzeroscan.com/oft/ASK/Permission), allowing for:

* Secure bridging between supported chains
* Unified liquidity across the Permission ecosystem
* Native compatibility with Stargate routers and liquidity pools

This Stargate integration ensures fast, gas-efficient transfers with enhanced user experience.

### ⚠️ Verification

Always verify ASK contract addresses through:

* This Gitbook
* [Permission.io](https://www.permission.io)
* Our verified channels (Twitter, Discord, Telegram)

Do **not** interact with contracts not listed here.

### 🛠 Technical Details

* **Omnichain Protocol:** LayerZero
* **Token Standard:** OFT-20 (ERC-20 compatible)
* **Bridging:** Stargate live
* **Omnichain Routing:** LayerZero messaging with canonical supply
* **Planned Expansions:** Ethereum Mainnet, Arbitrum, and other EVM-compatible chains

***


---

# 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://docs.permission.ai/ask-token/contract-addresses.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.
