# \[Tutorial\] Using Chainlink Token Manager on Kaia – Deploy CCTs without code

**URL:** <https://devforum.kaia.io/t/tutorial-using-chainlink-token-manager-on-kaia-deploy-ccts-without-code/8997>\
**Category:** Kaia\
**Created:** [12월 11, 2025, 8:46오전 UTC](https://devforum.kaia.io/t/tutorial-using-chainlink-token-manager-on-kaia-deploy-ccts-without-code/8997 "2025-12-11T08:46:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sean.lin](https://yyz1.discourse-cdn.com/flex035/user_avatar/devforum.kaia.io/sean.lin/32/3173_2.png) [@sean.lin](https://devforum.kaia.io/u/sean.lin)\
**Post date:** [12월 11, 2025, 8:46오전 UTC](https://devforum.kaia.io/t/tutorial-using-chainlink-token-manager-on-kaia-deploy-ccts-without-code/8997/1 "2025-12-11T08:46:30Z")

</div>

![20251209_Using Chainlink’s Token Manager on Kaia (EN) (1)](https://canada1.discourse-cdn.com/flex035/uploads/klaytn/original/2X/9/936705ddd3cfcf922af52adce9ecbc5ac90f1a64.jpeg)

**TL;DR:**  
Learn how to deploy or upgrade tokens to be cross-chain compatible using Chainlink’s no-code Token Manager interface.

As cross-chain interoperability becomes the default requirement for new projects, developers need a safe way to bridge assets without managing custom infrastructure.

**Chainlink Token Manager** provides a simple interface for creating production-ready tokens and configuring cross-chain transfers using CCIP. This guide walks you through the entire workflow, from wallet connection to final deployment.

**What is covered:**

- **Prerequisites:** Setting up a supported wallet and gas funds.

- **New Token Deployment:** Configuring details, supply caps, and selecting target networks (e.g., Kaia + Ethereum).

- **Existing Token Integration:** How to take a token already deployed on Kaia and enable the **Burn & Mint** mechanism for cross-chain transfers.

- **Management:** Managing token pools and verifying admin/ownership roles.

**Why use this?** It removes the need to write and audit custom bridge contracts, relying instead on the established security of the Chainlink CCIP network.

**Full step-by-step guide:** 👉 [https://medium.com/kaiachain/using-chainlinks-token-manager-on-kaia-9cc985208036](https://medium.com/kaiachain/using-chainlinks-token-manager-on-kaia-9cc985208036)

---

<div class="post-metadata">

**Author:** ![sean.lin](https://yyz1.discourse-cdn.com/flex035/user_avatar/devforum.kaia.io/sean.lin/32/3173_2.png) [@sean.lin](https://devforum.kaia.io/u/sean.lin)\
**Post date:** [12월 15, 2025, 9:48오전 UTC](https://devforum.kaia.io/t/tutorial-using-chainlink-token-manager-on-kaia-deploy-ccts-without-code/8997/2 "2025-12-15T09:48:32Z")

</div>

![Add an existing token](https://canada1.discourse-cdn.com/flex035/uploads/klaytn/original/2X/b/b233df276ca28853c5233fe0ddd3b2a76a68346c.jpeg)

 ![Deploy new token](https://canada1.discourse-cdn.com/flex035/uploads/klaytn/original/2X/3/3031ae417cf4a0b211ce192504e319cefdbbfc71.png)

Concrete scenario: you want your token available on Kaia **without maintaining custom bridge contracts** (upgrades, monitoring, security reviews, ongoing ops).

Things to think about:  
– Pick the right path early: **new token (deploy)** vs **existing token (add/register)** so you don’t redo setup later.  
– Treat the flow like production infra: confirm configs/roles, start small, then scale once you’re confident in the setup.  
– Plan ops from day 1: who owns updates, monitoring, and changes after launch?

**Mainnet only.** Full tutorial: [https://medium.com/kaiachain/using-chainlinks-token-manager-on-kaia-9cc985208036](https://medium.com/kaiachain/using-chainlinks-token-manager-on-kaia-9cc985208036)  
Questions welcome — drop your setup (new vs existing, source chain, token type), and we’ll reply in-thread.