> For the complete documentation index, see [llms.txt](https://docs.skylinebridge.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skylinebridge.tech/overview/technical-design/minting-and-burning-tokens-on-cardano-chains.md).

# Minting and Burning Tokens on Cardano Chains

When you bridge some tokens to a Cardano-type chain (such as Cardano or Apex Fusion Vector), Skyline doesn't pay them out of a pre-filled reserve. It **mints** new tokens for you on the destination chain. When you bridge those tokens back, the bridge takes them in and **burns** them, so the supply on the chain always matches what's backed by the bridge.

Minting is a powerful right: whoever holds it can create tokens. This page explains how Skyline makes sure that only the bridge validators, acting together, can ever use it.

## The three building blocks

### 1. The validators

Skyline is run by a set of independent validators. Each validator holds its own key. Nothing important happens on a Cardano chain unless at least two thirds of them (plus one) sign off on it. This group decision is called the **quorum**.

### 2. A validator-controlled address holding a unique NFT

The bridge keeps a special **multisignature address** on each Cardano chain. Like the bridge's other addresses, funds can only leave it when the validator quorum signs.

This address holds one thing that matters: a **gatekeeper NFT**. It is a one-of-a-kind token, created once when the bridge was set up. Its creation was locked after a deadline, so a second copy can never exist.

Think of the NFT as the key to the mint, and the multisignature address as the vault that holds the key.

### 3. The minting smart contract

The tokens themselves are governed by a small **smart contract** on the Cardano chain. Every time someone tries to mint or burn these tokens, the chain runs the contract, which checks two things:

* **Is the gatekeeper NFT part of this transaction?** If not, the mint or burn is rejected.
* **Is the NFT returned to the same address it came from?** If not, the mint or burn is rejected.

The contract code is public, so anyone can try to call it. Without the NFT, though, their attempt simply fails.

## How it all fits together

Putting the pieces together gives a simple chain of trust:

1. Tokens can only be minted or burned if the gatekeeper NFT takes part in the transaction.
2. The NFT can only take part if it's spent from the validator-controlled address.
3. That address can only be spent from if the validator quorum signs.

So **minting and burning require the agreement of the validator quorum**, and no single validator or outside party can do either on their own.

The second rule in the contract guarantees that the NFT goes straight back to the validator-controlled address whenever tokens are minted. It can't be quietly moved somewhere else.

## What happens when you bridge

**Bridging tokens to a Cardano chain.** Once the validators confirm your bridging request, they create a transaction that delivers your tokens. If the bridge doesn't already hold enough of them, the same transaction mints the difference. The gatekeeper NFT is part of the transaction and is returned to its address in the same step. The validators sign it, and the transaction is submitted to the chain.

**Bridging tokens back.** You send your tokens to the bridge's address on the Cardano chain. The bridge confirms your request and delivers your funds on the destination chain. The tokens you sent are held by the bridge, out of circulation, and are burned as part of a later bridge transaction. Burning follows exactly the same rules as minting: the NFT has to take part and the validators have to agree.

## What happens when the validator set changes

Validators can join or leave over time. When that happens, the validators' keys change, so the bridge gets a new validator-controlled address on the chain.

The plan is for the outgoing validators to approve one last transfer that moves everything, including the gatekeeper NFT, to the new address. From then on, the new validator set controls minting.

The smart contract only cares about the NFT, not about which address holds it. Moving the NFT therefore changes nothing for token holders. The tokens keep the same identity, the contract doesn't need to be redeployed, and no tokens need to be swapped.

## Summary

<table><thead><tr><th width="243">Guarantee</th><th>Why it holds</th></tr></thead><tbody><tr><td>Only the validators, together, can mint or burn</td><td>Minting needs the NFT, and the NFT sits at an address only the validator quorum can spend from.</td></tr><tr><td>Nobody else can use the minting contract</td><td>The contract rejects any transaction that doesn't include the one existing NFT.</td></tr><tr><td>The NFT can't be taken during a mint</td><td>The contract requires the NFT to go back to the address it came from.</td></tr><tr><td>Tokens stay the same when validators change</td><td>The NFT moves to the new validators' address, and the token's identity is tied to the NFT, not to the address.</td></tr></tbody></table>
