wormhole bridge transfer types: which fits your token?

Choose CCTP for native USDC where it is supported, NTT when an issuer wants its token to remain native across chains, and WTT when a wrapped representation fits, Wormhole’s documentation says. The wormhole bridge route depends on the token, destination chain and transfer options available to the app or wallet. These routes share Wormhole messaging, but they represent the asset differently on the destination.

Which wormhole bridge transfer type fits your token?

For native USDC, CCTP is the direct fit on supported chains because Circle’s Cross-Chain Transfer Protocol burns USDC on the source chain and mints native USDC on the destination. Wormhole’s CCTP documentation says transfers outside that supported route may instead use WTT, producing a Wormhole-wrapped token.

For a token issuer managing deployments across chains, NTT keeps control of token design and settings, according to Wormhole. For users moving other assets between supported chains, WTT is the general wrapped-token route.

How do WTT and NTT represent the token?

WTT uses a lock-and-mint model: the source token is locked and a corresponding wrapped token is created on the destination. On a return transfer, the wrapped representation can be burned and the source asset released. The destination asset is therefore a bridged representation, not necessarily the same token contract as on the source chain.

NTT lets issuers keep their token native on each supported chain. Wormhole’s documentation describes two deployment modes: tokens can be burned on the source and minted on the destination, or locked on the source and released from a destination balance. Issuers configure the model and can set controls such as rate limits.

What should you check before sending?

Start with the asset you need to receive, then confirm that the route supports both chains. A wormhole bridge transfer can also require a separate destination transaction, depending on the route; automatic delivery may be available for an added fee.

• For native USDC, check that CCTP supports the source and destination.
• For an issuer-managed token, check whether NTT is deployed on both chains.
• For WTT, confirm the destination token is the wrapped asset you intend to hold.
• Before confirming, verify the recipient address and whether you need destination-chain gas to complete delivery.

For most users, the practical choice follows the asset: CCTP for native USDC on its supported routes, NTT for issuer-controlled native tokens, and WTT where a wrapped version is acceptable. The available route and completion steps depend on the chains and app; check those details before sending.