You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: build/core-messaging/wormhole-relayers.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ To send a message to a contract on another EVM chain, you can call the `sendPayl
55
55
```
56
56
57
57
!!! tip
58
-
To reduce transaction confirmation time, you can lower the consistency level using the [`sendToEvm`](https://github.com/wormhole-foundation/wormhole/blob/{{repositories.wormhole.version}}/sdk/js/src/relayer/relayer/send.ts#L33){target=\_blank} method.
58
+
To reduce transaction confirmation time, you can lower the consistency level using the [`sendToEvm`](https://github.com/wormhole-foundation/wormhole/blob/v{{repositories.wormhole.version}}/sdk/js/src/relayer/relayer/send.ts#L33){target=\_blank} method.
59
59
60
60
The `sendPayloadToEvm` method is marked `payable` to receive fee payment for the transaction. The value to attach to the invocation is determined by calling the `quoteEVMDeliveryPrice`, which provides an estimate of the cost of gas on the target chain.
61
61
@@ -73,7 +73,7 @@ In total, sending a message across EVM chains can be as simple as getting a fee
73
73
74
74
### Receive a Message
75
75
76
-
To receive a message using a Wormhole relayer, the target contract must implement the [`IWormholeReceiver`](https://github.com/wormhole-foundation/wormhole-relayer-solidity-sdk/blob/main/src/interfaces/IWormholeReceiver.sol){target=\_blank} interface, as shown in the [previous section](#interacting-with-the-wormhole-relayer).
76
+
To receive a message using a Wormhole relayer, the target contract must implement the [`IWormholeReceiver`](https://github.com/wormhole-foundation/wormhole-relayer-solidity-sdk/blob/main/src/interfaces/IWormholeReceiver.sol){target=\_blank} interface, as shown in the [previous section](#interact-with-the-wormhole-relayer).
Copy file name to clipboardexpand all lines: build/multigov/upgrade-evm.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ MultiGov is designed to be flexible but stable. Due to the system's complexity a
10
10
## Key Considerations for Upgrades
11
11
12
12
-**`HubGovernor`**:
13
-
- Not upgradeable. A new deployment requires redeploying several components of the MultiGov system. Refer to the [Process for Major System Upgrade](/docs/build/multigov/upgrade/#process-for-major-system-upgrade) section for more details
13
+
- Not upgradeable. A new deployment requires redeploying several components of the MultiGov system. Refer to the [Process for Major System Upgrade](#process-for-major-system-upgrade) section for more details
14
14
15
15
-**`HubVotePool`**:
16
16
- Can be replaced by setting a new `HubVotePool` on the `HubGovernor`
Copy file name to clipboardexpand all lines: build/start-building/products.md
+15-15
Original file line number
Diff line number
Diff line change
@@ -18,27 +18,27 @@ Wormhole offers different solutions for cross-chain asset transfer, each designe
18
18
-[**Connect**](/docs/build/transfers/connect/overview/){target=\_blank} - a pre-built bridging UI for cross-chain token transfers, requiring minimal setup. Best for projects seeking an easy-to-integrate UI for bridging without modifying contracts
19
19
-[**Native Token Transfers (NTT)**](/docs/learn/transfers/native-token-transfers/overview/){target=\_blank} - a mechanism to transfer native tokens cross-chain seamlessly without conversion to wrapped asset. Best for projects that require maintaining token fungibility and native chain functionality across multiple networks
20
20
-[**Token Bridge**](/docs/learn/transfers/token-bridge/){target=\_blank} - a bridging solution that uses a lock and mint mechanism. Best for projects that need cross-chain liquidity using wrapped assets and the ability to send messages
21
-
-[**Wormhole Settlement**](/docs/learn/transfers/settlement/overview/){target=\_blank} - a next-generation suite of intent protocols enabling fast multichain transfers, optimizing liquidity flows and interoperability without relying on traditional bridging methods. Best for institutional-scale volume and chain abstraction for application developers
21
+
-[**Settlement**](/docs/learn/messaging/wormhole-settlement/overview/){target=\_blank} - intent-based protocols enabling fast multichain transfers, optimized liquidity flows, and interoperability without relying on traditional bridging methods
Copy file name to clipboardexpand all lines: build/toolkit/typescript-sdk/sdk-layout.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -315,7 +315,7 @@ VAAs are the backbone of Wormhole’s cross-chain communication. Each VAA is a s
315
315
The Wormhole SDK organizes the VAA structure into three key components:
316
316
317
317
-[**Header**](https://github.com/wormhole-foundation/wormhole-sdk-ts/blob/main/core/definitions/src/vaa/vaa.ts#L37-L41){target=\_blank} - contains metadata such as the Guardian set index and an array of Guardian signatures
318
-
-[**Envelope**](https://github.com/wormhole-foundation/wormhole-sdk-ts/blob/main/core/definitions/src/vaa/vaa.ts#L44-L51){target=\_blank} - includes chain-specific details such as the emitter chain, address, sequence, and [consistency (finality) level](/build/reference/consistency-levels/){target=\_blank}
318
+
-[**Envelope**](https://github.com/wormhole-foundation/wormhole-sdk-ts/blob/main/core/definitions/src/vaa/vaa.ts#L44-L51){target=\_blank} - includes chain-specific details such as the emitter chain, address, sequence, and [consistency (finality) level](/docs/build/reference/consistency-levels/){target=\_blank}
319
319
-**Payload** - provides application-specific data, such as the actual message or operation being performed
Copy file name to clipboardexpand all lines: build/transfers/connect/configuration-v0.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Configure Your Connect Widget: v0
2
+
title: Configure Your Connect Widget v0
3
3
description: Configure Wormhole Connect v0 for React or HTML, set themes, define tokens, networks, and customize RPC endpoints for optimized blockchain interactions.
Copy file name to clipboardexpand all lines: build/transfers/native-token-transfers/cli-commands.md
+26-2
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,13 @@ description: A comprehensive guide to the Native Token Transfers (NTT) CLI, deta
9
9
10
10
The NTT Command-Line Interface (CLI) is a powerful tool for managing native token transfers across multiple blockchain networks within the Wormhole ecosystem. This page provides a comprehensive list of available commands, their descriptions, and examples to help you interact with and configure the NTT system effectively. Whether initializing deployments, updating configurations, or working with specific chains, the NTT CLI simplifies these operations through its intuitive commands.
11
11
12
+
If you haven't installed the NTT CLI yet, follow the [NTT Installation Guide](/docs/build/transfers/native-token-transfers/deployment-process/installation/#installation){target=\_blank} to set it up before proceeding.
13
+
12
14
## Table of Commands
13
15
14
16
The following table lists the available NTT CLI commands, descriptions, and examples.
15
17
16
-
!!! note
17
-
To explore detailed information about any NTT CLI command, including its options and examples, you can append `--help` to the command. This will display a comprehensive guide for the specific command.
18
+
To explore detailed information about any NTT CLI command, including its options and examples, you can append `--help` to the command. This will display a comprehensive guide for the specific command.
18
19
19
20
### General Commands
20
21
@@ -45,3 +46,26 @@ The following table lists the available NTT CLI commands, descriptions, and exam
|`ntt solana token-authority <programId>`| print the token authority address for a given program ID|`ntt solana token-authority Sol1234...`|
47
48
|`ntt solana ata <mint> <owner> <tokenProgram>`| print the token authority address for a given program ID|`ntt solana ata Mint123... Owner123... token22`|
Copy file name to clipboardexpand all lines: build/transfers/native-token-transfers/deployment-process/installation.md
+41-16
Original file line number
Diff line number
Diff line change
@@ -5,39 +5,41 @@ description: Learn how to Install Wormhole’s Native Token Transfers (NTT) fram
5
5
6
6
# Install the Native Token Transfers CLI
7
7
8
-
## Installation
9
-
10
-
In this video, the Wormhole team walks you through installing the Native Token Transfers (NTT) CLI. You’ll see a practical demonstration of running commands, verifying your installation, and addressing common issues that might arise. If you prefer to follow written instructions or want a quick reference for each step, scroll down for the detailed installation guide.
8
+
In this video, the Wormhole team walks you through installing the [Native Token Transfers (NTT) CLI](https://github.com/wormhole-foundation/native-token-transfers/tree/main/cli){target=\_blank}. You’ll see a practical demonstration of running commands, verifying your installation, and addressing common issues that might arise. If you prefer to follow written instructions or want a quick reference for each step, scroll down for the detailed installation guide.
3. Once installed, check out the available [NTT CLI Commands](/docs/build/transfers/native-token-transfers/cli-commands/){target=\_blank} to start using the CLI
30
33
31
-
### Updating
34
+
## Update NTT CLI
32
35
33
-
To update an existing NTT CLI installation, run:
36
+
To update an existing NTT CLI installation, run the following commandin your terminal:
34
37
35
38
```bash
36
39
ntt update
37
40
```
38
41
39
-
!!! note
40
-
NTT CLI installations and updates will always pick up the latest tag with name vX.Y.Z+cli and verify that the underlying commit is included in main.
42
+
NTT CLI installations and updates will always pick up the latest tag with name vX.Y.Z+cli and verify that the underlying commit is included in main.
41
43
42
44
For local development, you can update your CLI version from a specific branch or install from a local path.
Git branch and local installations enable a fast iteration loop as changes to the CLI code will immediately be reflected in the running binary without having to run any build steps.
58
+
59
+
## Where to Go Next
60
+
61
+
<div class="grid cards" markdown>
62
+
63
+
64
+
- :octicons-tools-16:{ .lg .middle } **Deploy to EVM Chains**
65
+
66
+
---
67
+
68
+
Deploy and configure Wormhole’s Native Token Transfers (NTT) for EVM chains, including setup, token compatibility, mint/burn modes, and CLI usage.
69
+
70
+
[:custom-arrow: Deploy NTT to EVM chains](/docs/build/transfers/native-token-transfers/deployment-process/deploy-to-evm/)
71
+
72
+
- :octicons-tools-16:{ .lg .middle } **Deploy to Solana**
73
+
74
+
---
75
+
76
+
Deploy and configure Wormhole's Native Token Transfers (NTT) for Solana, including setup, token compatibility, mint/burn modes, and CLI usage.
77
+
78
+
[:custom-arrow: Deploy NTT to Solana](/docs/build/transfers/native-token-transfers/deployment-process/deploy-to-solana/)
Copy file name to clipboardexpand all lines: build/transfers/native-token-transfers/deployment-process/post-deployment.md
+15-9
Original file line number
Diff line number
Diff line change
@@ -3,20 +3,26 @@ title: Native Token Transfers Post Deployment
3
3
description: Learn post-deployment guidelines for optimizing Wormhole NTT, which include testing, security, frontend integration, ecosystem coordination, and monitoring.
4
4
---
5
5
6
-
# Native Token Transfers (NTT) Post Deployment
6
+
# Native Token Transfers Post Deployment
7
7
8
-
## Post Deployment Recommendations
9
-
10
-
To offer the best user experience and ensure the most robust deployment, Wormhole contributors recommend the following after you have deployed NTT:
8
+
To offer the best user experience and ensure the most robust deployment, Wormhole contributors recommend the following after you have deployed Native Token Transfers (NTT):
11
9
12
10
- Implement a robust testing plan for your multichain token before launching
13
-
- Ensure comprehensive, documented security measures are followed regarding custody of contract ownership, control of keys, and access control roles. Check the [NTT configuration](/docs/build/transfers/native-token-transfers/configuration/){target=\_blank} for more details on ownership and rate limits
14
-
- Consider a streamlined, customizable frontend such as [Wormhole Connect](https://connect-in-style.wormhole.com/){target=\_blank} for an optimized user experience
15
-
- Alternatively the [Wormhole SDK](/docs/build/toolkit/typescript-sdk/){target=\_blank} allows for a direct integration into your infrastructure
16
-
- Ensure ecosystem actors such as block explorers, automated security tools (such as BlockAid and Blowfish), wallets (such as MetaMask, Backpack, and Phantom) are aware of your multichain deployment and that it is labeled appropriately
11
+
- Ensure comprehensive, documented security measures are followed for custody of contract ownership, control of keys, and access control roles. Check the [NTT configuration](/docs/build/transfers/native-token-transfers/configuration/){target=\_blank} for more details on ownership and rate limits
12
+
- Consider a streamlined, customizable frontend such as [Wormhole Connect](/docs/build/transfers/connect/){target=\_blank} for an optimized user experience
13
+
- Alternatively, the [Wormhole TypeScript SDK](/docs/build/toolkit/typescript-sdk/){target=\_blank} allows for a direct integration into your infrastructure
14
+
- Ensure ecosystem actors such as block explorers, automated security tools (such as BlockAid and Blowfish), and wallets (such as MetaMask, Backpack, and Phantom) are aware of your multichain deployment and that it is labeled appropriately
17
15
- Monitor and maintain your multichain deployment
18
16
19
-
## Post Deployment Integration Demos
17
+
## Manual Relaying for Solana Transfers
18
+
19
+
By default, NTT transfers to Solana require manual relaying, meaning that after initiating a cross-chain transfer, the recipient must submit an on-chain transaction to claim the tokens.
20
+
21
+
This step ensures that tokens are properly minted or unlocked on Solana and prevents unauthorized claims.
22
+
23
+
[Wormhole Connect](/docs/build/applications/connect/){target=\_blank} support this process automatically.
Copy file name to clipboardexpand all lines: build/transfers/native-token-transfers/faqs.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ description: Frequently asked questions about Wormhole Native Token Transfers, i
7
7
8
8
## Do you have an example of how cross-chain lending can be implemented using Wormhole?
9
9
10
-
Yes, we have an example of cross-chain lending that leverages [Wormhole’s Token Bridge](/learn/transfers/token-nft-bridge/){target=\_blank}. In this example, collateral deposits (such as ETH on Ethereum) are bridged to a hub chain. Once the collateral is deposited, the borrowed assets, like wrapped BNB, are bridged to Binance Smart Chain. You can explore the full implementation in this [cross-chain lending example repository](https://github.com/wormhole-foundation/example-wormhole-lending){target=_blank}.
10
+
Yes, we have an example of cross-chain lending that leverages [Wormhole’s Token Bridge](/docs/learn/transfers/token-bridge/){target=\_blank}. In this example, collateral deposits (such as ETH on Ethereum) are bridged to a hub chain. Once the collateral is deposited, the borrowed assets, like wrapped BNB, are bridged to Binance Smart Chain. You can explore the full implementation in the [Wormhole Lending Examples repository](https://github.com/wormhole-foundation/example-wormhole-lending){target=_blank} on GitHub.
11
11
12
-
Alternatively, you can also implement cross-chain lending using [Wormhole’s core messaging](/learn/transfers/native-token-transfers/){target=\_blank} instead of the Token Bridge, which avoids the limitations imposed by governor limits. ETH would be custodied on Ethereum, and BNB on the Binance spoke during this setup. When a user deposits ETH on Ethereum, a core bridge message is sent to the hub for accounting purposes. The hub then emits a message that can be redeemed on Binance to release the BNB. This approach allows for more direct asset control across chains while reducing reliance on Token Bridge limits.
12
+
Alternatively, you can also implement cross-chain lending using [Wormhole’s core messaging](/docs/learn/transfers/native-token-transfers/){target=\_blank} instead of the Token Bridge, which avoids the limitations imposed by governor limits. ETH would be custodied on Ethereum, and BNB on the Binance spoke during this setup. When a user deposits ETH on Ethereum, a core bridge message is sent to the hub for accounting purposes. The hub then emits a message that can be redeemed on Binance to release the BNB. This approach allows for more direct asset control across chains while reducing reliance on Token Bridge limits.
13
13
14
14
## What causes the "No protocols registered for Evm" error in Wormhole SDK?
15
15
@@ -25,7 +25,7 @@ By importing this package, the Wormhole SDK can register and utilize the require
25
25
26
26
## How can I transfer ownership of NTT to a multisig?
27
27
28
-
Transferring ownership of Wormhole's NTT to a multisig is a two-step process for safety. This ensures that ownership is not transferred to an address that cannot claim it. Refer to the `transfer_ownership` method in the [NTT Manager Contract](https://github.com/wormhole-foundation/native-token-transfers/blob/main/solana/programs/example-native-token-transfers/src/instructions/admin.rs#L16-L60){target=\_blank} to initiate the transfer.
28
+
Transferring ownership of Wormhole's NTT to a multisig is a two-step process for safety. This ensures that ownership is not transferred to an address that cannot claim it. Refer to the `transfer_ownership` method in the [NTT Manager Contract](https://github.com/wormhole-foundation/native-token-transfers/blob/main/solana/programs/example-native-token-transfers/src/instructions/admin/transfer_ownership.rs#L55){target=\_blank} to initiate the transfer.
29
29
30
30
1.**Initiate transfer** - use the `transfer_ownership` method on the NTT Manager contract to set the new owner (the multisig)
31
31
2.**Claim ownership** - the multisig must then claim ownership via the `claim_ownership` instruction. If not claimed, the current owner can cancel the transfer
Copy file name to clipboardexpand all lines: build/transfers/token-bridge.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ description: Learn how to integrate Wormhole's Token Bridge for seamless multich
7
7
8
8
## Introduction
9
9
10
-
Wormhole's Token Bridge enables seamless cross-chain token transfers using a lock-and-mint mechanism. The bridge locks tokens on the source chain and mints them as wrapped assets on the destination chain. Additionally, the Token Bridge supports [contract-controlled transfers (transfers with messages)](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}, where arbitrary byte payloads can be attached to the token transfer, enabling more complex chain interactions.
10
+
Wormhole's Token Bridge enables seamless cross-chain token transfers using a lock-and-mint mechanism. The bridge locks tokens on the source chain and mints them as wrapped assets on the destination chain. Additionally, the Token Bridge supports [Token Transfers with Messages](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}, where arbitrary byte payloads can be attached to the token transfer, enabling more complex chain interactions.
11
11
12
12
This page outlines the core contract methods needed to integrate Token Bridge functionality into your smart contracts. To understand the theoretical workings of the Token Bridge, refer to the [Token Bridge](/docs/learn/transfers/token-bridge/){target=\_blank} page in the Learn section.
13
13
@@ -24,7 +24,7 @@ The primary functions of the Token Bridge contracts revolve around:
24
24
25
25
-**Attesting a token** - registering a new token for cross-chain transfers
26
26
-**Transferring tokens** - locking and minting tokens across chains
27
-
-**Transferring tokens with a payload** - including additional data for contract-controlled transfers
27
+
-**Transferring tokens with a payload** - including additional data with transfers
28
28
29
29
### Attest a token
30
30
@@ -245,4 +245,4 @@ You can refer to the [core-bridge repository](https://github.com/nonergodic/core
245
245
246
246
Updating the metadata (such as the token image, name, or symbol) of a wrapped token on [Solscan](https://solscan.io/){target=\_blank} requires [contacting the Solscan team](https://solscan.io/contactus){target=\_blank} directly. Wormhole cannot make these updates for you because the wrapped token contracts are owned and controlled by the Token Bridge, not individual developers or projects.
247
247
248
-
To request an update, contact Solscan via [support@solscan.io](mailto:support@solscan.io) or their [contact form](https://solscan.io/contactus){target=\_blank}.
248
+
To request an update, contact Solscan via [support@solscan.io](mailto:support@solscan.io) or their [contact form](https://solscan.io/contactus){target=\_blank}.
Copy file name to clipboardexpand all lines: learn/glossary.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ A Spy is a daemon that eavesdrops on the messages passed between Guardians, typi
65
65
66
66
## VAA
67
67
68
-
[Verifiable Action Approvals](/docs/learn/infrastructure/vaas/){target=\_blank} (VAAs) are the base data structure in the Wormhole ecosystem. They contain the messages emitted by [xDapps](#xdapp) along with information such as what contract emitted the message.
68
+
[Verifiable Action Approvals](/docs/learn/infrastructure/vaas/){target=\_blank} (VAAs) are the base data structure in the Wormhole ecosystem. They contain emitted messages along with information such as what contract emitted the message.
- :octicons-rocket-16:{ .lg .middle } **Deploy to EVM Chains**
53
53
54
54
---
55
55
56
-
Set up and deploy MultiGov locally with step-by-step instructions for configuring, compiling, and deploying smart contracts across chains.
56
+
Set up and deploy MultiGov on EVM chains with step-by-step instructions for configuring, compiling, and deploying smart contracts across chains.
57
57
58
-
[:custom-arrow: Discover how to deploy MultiGov](/docs/build/multigov/deployment/)
58
+
[:custom-arrow: Discover how to deploy MultiGov](/docs/build/multigov/deploy-to-evm/)
59
+
60
+
- :octicons-rocket-16:{ .lg .middle } **Deploy to Solana**
61
+
62
+
---
63
+
64
+
Set up and deploy the MultiGov Staking Program on Solana with step-by-step instructions for configuring, funding, deploying, and initializing the program.
65
+
66
+
[:custom-arrow: Discover how to deploy MultiGov on Solana](/docs/build/multigov/deploy-to-solana/)
Copy file name to clipboardexpand all lines: learn/infrastructure/relayer.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ Users themselves carry out the three steps of the cross-chain process:
64
64
65
65
Custom relayers are purpose-built components within the Wormhole protocol, designed to relay messages for specific applications. They are capable of performing off-chain computations and can be customized to suit a variety of use cases.
66
66
67
-
The main method of setting up a custom relayer is by listening directly to the Guardian Network via a [Spy](/learn/infrastructure/spy/).
67
+
The main method of setting up a custom relayer is by listening directly to the Guardian Network via a [Spy](/docs/learn/infrastructure/spy/).
Copy file name to clipboardexpand all lines: learn/transfers/settlement/architecture.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -99,4 +99,4 @@ The protocol provides mechanisms for unlocking the fee once the bridging process
99
99
## Where to Go Next
100
100
101
101
- To learn more about available EVM functions, see the [Build on the Wormhole Liquidity Layer](/docs/build/transfers/settlement/liquidity-layer/){target=\_blank} guide
102
-
- To learn how to integrate settlement routes into your application, see the [Integrate Wormhole Settlement Routes Using the SDK](https://github.com/wormhole-foundation/demo-mayanswift){target=\_blank} tutorial
102
+
- To learn how to integrate settlement routes into your application, see the [Integrate Wormhole Settlement Routes Using the SDK](https://github.com/wormhole-foundation/demo-mayanswift){target=\_blank} tutorial
Copy file name to clipboardexpand all lines: learn/transfers/token-bridge.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Transferring tokens across blockchain networks is challenging due to the lack of
9
9
10
10
Wormhole’s Token Bridge addresses these challenges by providing a decentralized protocol for seamless cross-chain token transfers through a lock-and-mint mechanism. Using Wormhole’s message-passing protocol, the Token Bridge allows standards-compliant tokens, like ERC-20 on Ethereum or SPL on Solana, to be transferred between different blockchains while preserving their original attributes.
11
11
12
-
Offering a more efficient, scalable, and secure alternative to traditional solutions, the Token Bridge ensures that assets retain their properties across multiple blockchain ecosystems. Additionally, it supports flexible features like [Contract Controlled Transfers](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}, enabling custom interactions by allowing tokens to carry additional data for smart contract integration on the destination chain.
12
+
Offering a more efficient, scalable, and secure alternative to traditional solutions, the Token Bridge ensures that assets retain their properties across multiple blockchain ecosystems. Additionally, it supports flexible features like [Token Transfers with Messages](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}, enabling custom interactions by allowing tokens to carry additional data for smart contract integration on the destination chain.
13
13
14
14
This page introduces the core concepts and functions of Wormhole’s Token Bridge, explaining how it operates, its key features, and how it enables secure and efficient cross-chain token transfers.
15
15
@@ -21,7 +21,7 @@ Before a token can be transferred to a new chain, the token’s metadata must be
21
21
22
22
While the [Core Contract](/docs/learn/infrastructure/core-contracts/){target=\_blank} has no specific receiver by default, transfers sent through the Token Bridge do have a specific receiver chain and address to ensure the tokens are minted to the expected recipient.
23
23
24
-
In addition to standard token transfers, the Token Bridge supports [Contract Controlled Transfers](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}. This functionality allows users to attach additional data to token transfers, enabling more complex interactions with smart contracts on the destination chain. For instance, a token transfer can include a payload that triggers specific actions, such as interacting with a decentralized exchange (DEX) or automated market maker (AMM).
24
+
In addition to standard token transfers, the Token Bridge supports [Token Transfers with Messages](/docs/learn/infrastructure/vaas/#token-transfer-with-message){target=\_blank}. This functionality allows users to attach additional data to token transfers, enabling more complex interactions with smart contracts on the destination chain. For instance, a token transfer can include a payload that triggers specific actions, such as interacting with a decentralized exchange (DEX) or automated market maker (AMM).
Copy file name to clipboardexpand all lines: tutorials/by-product/wormhole-sdk/usdc-via-cctp.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: Learn how to perform USDC cross-chain transfers using Wormhole SDK
9
9
10
10
## Introduction
11
11
12
-
In this guide, we will show you how to bridge native USDC across different blockchain networks using [Circle's Cross-Chain Transfer Protocol](/learn/transfers/cctp/){target=\_blank} (CCTP) and [Wormhole’s TypeScript SDK](https://github.com/wormhole-foundation/wormhole-sdk-ts/tree/main){target=\_blank}.
12
+
In this guide, we will show you how to bridge native USDC across different blockchain networks using [Circle's Cross-Chain Transfer Protocol](/docs/learn/transfers/cctp/){target=\_blank} (CCTP) and [Wormhole’s TypeScript SDK](https://github.com/wormhole-foundation/wormhole-sdk-ts/tree/main){target=\_blank}.
13
13
14
14
Traditionally, cross-chain transfers using CCTP involve multiple manual steps, such as initiating the transfer on the source chain, relaying messages between chains, and covering gas fees on both the source and destination chains. Without the TypeScript SDK, developers must handle these operations independently, adding complexity and increasing the chance for errors, mainly when dealing with gas payments on the destination chain and native gas token management.
0 commit comments