# UTS Connector

The UTS Connector is designed to add cross-chain bridging capabilities to your tokens.  If you want to add bridging capabilities to an already deployed token, the Connector is the solution. Once deployed, it allows tokens to be locked on one chain and unlocked on another, facilitating the creation or release of UTS tokens. You can use the provided contract as it is or adjust it to suit your needs. To get started, simply deploy the Connector, and you'll be able to bridge tokens seamlessly.

{% hint style="info" %}
For additional technical details, you can explore the [UTSConnector.sol](https://github.com/Entangle-Protocol/uts-sc-v1/blob/main/contracts/ERC20/connector/UTSConnector.sol) contract on GitHub.
{% endhint %}

Below are two types of Connectors you can choose from based on your needs:

* **Connector with** [**Lock/Unlock Mechanism**](/universal-token-standard/developer-guides/manual-deploy/examples/uts-connector/lock-and-unlock-connector-scheme.md): If you do not want or cannot provide mint/burn access to the Connector, this option allows you to control the token’s locking and unlocking functions. Use this when you prefer to restrict token minting or burning but still want to enable bridging.
* **Connector with** [**Mint/Burn Mechanism**](/universal-token-standard/developer-guides/manual-deploy/examples/uts-connector/mint-and-burn-connector-scheme.md): Choose this option if you're able to provide mint and burn access to the Connector. It allows the Connector to mint and burn tokens during the bridging process.
* **Connector Based on** [**Native Currency**](/universal-token-standard/developer-guides/manual-deploy/examples/uts-connector/connector-over-native-currency.md): This type of Connector is built over the native currency of a blockchain, using the native token as the underlying asset for bridging.

<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>Mint &#x26; Burn Connector Scheme</td><td><a href="/files/SzCqoASuVOkUYU3Lhe1u">/files/SzCqoASuVOkUYU3Lhe1u</a></td><td><a href="/pages/4ewTX2iYlw9GiWVE4F7K">/pages/4ewTX2iYlw9GiWVE4F7K</a></td></tr><tr><td>Lock &#x26; Unlock Connector Scheme</td><td><a href="/files/D5xkrDh1IqLQDjEpEc3w">/files/D5xkrDh1IqLQDjEpEc3w</a></td><td><a href="/pages/0rkpgaSqs6R1yaYqMUJI">/pages/0rkpgaSqs6R1yaYqMUJI</a></td></tr><tr><td>Connector Over Native Currency</td><td><a href="/files/W98mhiYNt529uML6xviH">/files/W98mhiYNt529uML6xviH</a></td><td><a href="/pages/DTo1asfZtjyWu9ODwYI7">/pages/DTo1asfZtjyWu9ODwYI7</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-connector.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.