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`|
0 commit comments