Chainlink CCIP

TNZO as a CCIP Cross-Chain Token: lock on Tenzro, burn and mint on the external chain, governed rate limits and fees in TNZO.

Chainlink CCIP (Cross-Chain Interoperability Protocol) is the ccip transport behind Tenzro's governed bridge routes. On a CCIP route TNZO follows the CCIP Cross-Chain Token model: on Tenzro the route holds TNZO locked against the representation, and on the external chain the representation is a burn/mint ERC-20 behind a burn/mint token pool registered in that chain's token admin registry. The pool names Tenzro's endpoint on the lane as its remote pool and remote token.

How a transfer moves

Direction	On Tenzro	On the external chain
Out	The holder signs a bridge transaction; TNZO is locked in the route's vault and an outbound message is stored for relayers	The off-ramp executes the message and the token pool mints the representation
Back	The route committee's signed delivery is submitted by a relayer; TNZO is released to the recipient	A `ccipSend` on the router burns the representation

The representation's total supply on the external chain always equals what the route records as outstanding, and it can never exceed the TNZO locked on Tenzro for that chain.

Verification

An inbound delivery is accepted only if the route committee's threshold signed it, its nonce has not been used, it has not expired, the route is open, and it stays within the route's caps and the amount outstanding on the other chain. Where the route requires a light-client proof, the delivery must carry one as well. Outbound, messages leave Tenzro only from finalised blocks, backed by portable finality certificates.

Sending and receiving

bash

# Read the CCIP route to Ethereum: caps, epoch usage, lane buckets, locked and outstanding supply
tenzro bridge route --adapter ccip --chain ethereum --rpc https://rpc.tenzro.com

# Send 1 TNZO to an address on Ethereum (amount in wei), signed by your hardware key
tenzro bridge send --target-chain ethereum --recipient 0xRECIPIENT \
  --amount 1000000000000000000 --rpc https://rpc.tenzro.com

# Relayers: submit an attested inbound delivery
tenzro bridge deliver --adapter ccip --from-chain ethereum --delivery <DELIVERY_HEX> \
  --rpc https://rpc.tenzro.com

Each external chain is served by exactly one route, so --target-chain selects the CCIP route when the chain is served over CCIP. A CCIP route can also carry listed stablecoins such as USDC; pass --asset USDC to send the representation back to the chain it came from.

Rate limits

Every route has a cap per transfer and a limit per epoch, and a network-wide limit bounds every route as well; the tighter applies. A CCIP route also carries its lane's token-bucket state, inbound and outbound, as the pools on the external chain enforce it. tenzro bridge route shows the buckets as they stand now. Check the remaining capacity before a large transfer and split it if it would exceed the limit.

Fees in TNZO

Quote the destination-native fee in TNZO: