> For the complete documentation index, see [llms.txt](https://yuzu-money.gitbook.io/yuzu-money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yuzu-money.gitbook.io/yuzu-money/security-infrastructure/chainlink-ccip-transporter-bridge.md).

# Chainlink CCIP (Transporter Bridge)

<figure><img src="/files/6FHBF2ZrQ5nT6rnu0gYa" alt=""><figcaption></figcaption></figure>

> [*Chainlink*](https://chain.link/) *is the cross-chain interoperability standard built on Chainlink's Decentralized Oracle Networks (DONs) — the same oracle infrastructure Chainlink reports has enabled over $16 trillion in total value (TVE) across DeFi and traditional finance. CCIP secures cross-chain messaging and token transfers for leading protocols and institutional pilots, and underpins* [*Transporter*](https://www.transporter.io/)*, its flagship bridging application.*

Yuzu Money uses Chainlink CCIP to carry Yuzu Alpha (syzUSD) and Yuzu Prime (yzPrime) using the **Cross-Chain Token (CCT) standard**. Under CCT, Yuzu deploys and owns its own token pools — retaining full control of the bridge contracts, transfer mechanics, and per-lane rate limits. Cross-chain transfers are executed through **Transporter**, the CCIP-native bridge front-end.

### **Chainlink Token Manager**

| Token                 | Standard               | Chainlink Token Manager                                                                                                                                     |
| --------------------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Staked yzUSD (syzUSD) | CCIP Cross-Chain Token | [Plasma <> Monad / Ethereum / HyperEVM / Sei / Pharos](https://tokenmanager.chain.link/dashboard/plasma-mainnet,0xc8a8df9b210243c55d31c73090f06787ad0a1bf6) |
| Yuzu Prime (yzPrime)  | CCIP Cross-Chain Token | [Monad <> Ethereum](https://tokenmanager.chain.link/dashboard/ethereum-mainnet,0xea14a0f64412af9a411a7e8543913376337c0e06)                                  |

The Token Manager dashboards are the authoritative source for each token's live pool addresses, supported lanes, transfer mechanism, and configured rate limits.

### **Why CCIP**

**Issuer-owned infrastructure:** Yuzu retains complete ownership of its token contracts, token pools, and implementation logic. There is no vendor lock-in and no hard-coded external dependency — the bridge configuration is Yuzu's to manage across every chain.

**Configurable rate limits:** Each token pool enforces a rate limit with a maximum capacity and a refill rate, set per lane. This caps the value that can move across any single pathway in a given window — a hard, issuer-controlled ceiling on the blast radius of any anomaly, independent of the transport layer.

**No liquidity pools, zero slippage:** CCT uses audited burn/mint (or lock/mint) token pools rather than pooled liquidity. The exact amount sent on the source chain is the exact amount received on the destination chain, with no slippage and no fragmented liquidity to defend.

{% hint style="info" %}
A bridge fails safely only when the layer that *moves* value is separate from the layer that can *stop* it. In CCIP, message transport runs through the oracle networks, while the on-chain risk safeguard and Yuzu's own per-lane rate limits sit outside that path — so a fault in transport cannot translate into unbounded loss.
{% endhint %}

### Security Model

CCIP is secured by Chainlink's Decentralized Oracle Networks and follows a defense-in-depth design, where independent layers each have to hold for a transfer to complete.

**Committing DON:** Observes and validates source-chain events and builds a consensus report of pending messages. No single node can commit a message; the report requires agreement across the oracle network.

**Executing DON:** Independently validates committed messages and executes them on the destination chain, releasing or minting tokens only against a verified commit report.

**On-chain Risk Management safeguard:** CCIP retains an on-chain Risk Management contract that acts as an emergency circuit-breaker over per-chain and network-wide functions, able to halt activity when required.

**Rate limits and monitoring:** Issuer-configured token-pool rate limits and continuous monitoring bound the exposure of any single lane and surface anomalies for response.