# UTS Token

The **UTS Token** is designed to be bridgeable by default. Once you create it, you can immediately begin bridging it across networks. You can use the provided implementation as-is or customize it to suit your needs.

{% hint style="info" %}
A key feature of the UTSToken is its ability to override the `_update` function to restrict burning access. For additional technical details, you can explore the [UTSToken.sol](https://github.com/Entangle-Protocol/uts-sc-v1/blob/main/contracts/ERC20/token/UTSToken.sol) contract on GitHub.
{% endhint %}

In this section, we’ll provide examples of two types of tokens: a [simple token](/universal-token-standard/developer-guides/manual-deploy/examples/uts-token/simple-token.md) and a [token that uses cross-chain messages](/universal-token-standard/developer-guides/manual-deploy/examples/uts-token/token-with-messages.md), allowing you to bridge tokens to multiple addresses in a single transaction.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Simple Token</td><td><a href="/files/ukwYyHnlgei9fFwINp1Y">/files/ukwYyHnlgei9fFwINp1Y</a></td><td><a href="/pages/RYW8PCEetxa2FzcArzk0">/pages/RYW8PCEetxa2FzcArzk0</a></td></tr><tr><td>Token with Messages</td><td><a href="/files/c1BOPgDRckcX1u44NlEJ">/files/c1BOPgDRckcX1u44NlEJ</a></td><td><a href="/pages/GksTOfvsYuAarI2OKRjt">/pages/GksTOfvsYuAarI2OKRjt</a></td></tr></tbody></table>


---

# Agent Instructions: 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://docs.entangle.fi/universal-token-standard/developer-guides/manual-deploy/examples/uts-token.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.