Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh build ntt index page #321

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Conversation

dawnkelly09
Copy link
Collaborator

Description

This PR does the following:

  • adds Quickstart section featuring NTT Launchpad to this page for easier discovery
  • adds timeline element linking to NTT guides for those who don't want to use Launchpad UI

Note: I did not add a Where to Go Next as we currently don't have an NTT tutorial I can add.

Checklist

  • [x ] Required - I have added a label to this PR 🏷️
  • [ x] Required - I have run my changes through Grammarly
  • [ n/a] If pages have been moved, I have created redirects in the wormhole-mkdocs repo

eshaben and others added 9 commits February 19, 2025 00:36
* add settlement to learn section

* add settlement to buil section

* fix links

* liquidity layer code snippets

* solver snippets

* llms

---------

Co-authored-by: Ilaria Enache <ilaria@Host-009.homenet.telecomitalia.it>
* adds connect index page to new IA

* tweaks admonition usage on /docs/build/transfers/connect/overview/

* moves timeline into snippet, left aligned

* feedback per review

* llms

* edits per feedback

* improve intro

* edits per feedback

* applies review feedback

* Apply suggestions from code review

Co-authored-by: Erin Shaben <eshaben@icloud.com>

---------

Co-authored-by: Erin Shaben <eshaben@icloud.com>
* adds token bridge build page in the new ai and fixes links

* Update build/transfers/token-bridge.md

Co-authored-by: Lucas Malizia <131050418+0xlukem@users.noreply.github.com>

* Update build/transfers/token-bridge.md

Co-authored-by: Lucas Malizia <131050418+0xlukem@users.noreply.github.com>

---------

Co-authored-by: Ilaria Enache <ilaria@Host-009.homenet.telecomitalia.it>
Co-authored-by: Lucas Malizia <131050418+0xlukem@users.noreply.github.com>
@dawnkelly09 dawnkelly09 added A1 - Maintenance Major Pull request contains major updates to an existing page (i.e., adding a new section, reorgs, etc.) B0 - Needs Review Pull request is ready for review labels Mar 20, 2025
@dawnkelly09 dawnkelly09 requested a review from eshaben as a code owner March 20, 2025 17:44
Visit the [Use Cases](/docs/build/start-building/use-cases/){target=\_blank} and [Product Comparison](/docs/build/start-building/products/){target=\_blank} pages for help determining if NTT will meet the needs of your project.

## Quickstart

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The NTT Launchpad is currently available only for EVM Chains. I think it's worth mentioning here.

@@ -9,7 +9,7 @@ Transferring tokens across blockchain networks is challenging due to the lack of

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.

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.
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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
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 Payload](/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.

Payload is more accurate. Why are we moving from Payload to Messages?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idk, actually. @ilariae or @eshaben ?

Copy link
Collaborator

@ilariae ilariae Mar 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we moved from "contract-controlled transfers" to "token transfer with message" last week, payload sounds also good but we need to be consistent everywhere with this

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, if you feel strongly about payloads, please open a separate PR making this change across the board

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really sure why these changes are showing up in this PR since this was done separately and should be what's on main already

@@ -5,27 +5,43 @@ description: This section provides comprehensive guidance on configuring, deploy

# Native Token Transfers

## Get Started
Native Token Transfers (NTT) simplify and enable seamless, flexible token transfers across blockchains. This section provides comprehensive guidance on configuring, deploying, and managing your NTT integration. It includes information relevant to both new token deployments and existing token management.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

simplies and enables? Since Native Token Transfers is a framework?

Comment on lines +14 to +24
The [Native Token Transfers (NTT) Launchpad](https://ntt.wormhole.com/){target=\_blank} is a Wormhole-managed UI application that provides a step-by-step interface for deploying NTT across multiple blockchains. NTT Launchpad replaces manually deploying contracts or configuring relayers for each chain. Create new multichain tokens or integrate existing tokens with just a few clicks.

<div class="grid cards" markdown>

- :octicons-rocket-16:{ .lg .middle } **Deployment Process**
- :octicons-tools-16:{ .lg .middle } **Deploy Native Token Transfers with Launchpad**

---

Guidance on installation, deployment to EVM and Solana, and maintaining your NTT after deployment.
Follow this guide to launch a new multichain token or integrate existing tokens for multichain use using NTT Launchpad, a step-by-step UI for deploying NTT across multiple blockchains.

[:custom-arrow: Deploy NTT with Launchpad](/docs/build/transfers/native-token-transfers/deployment-process/evm-launchpad/)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having the card and the text above is a little repetitive


Visit the following guides if you prefer to code your NTT integration directly:

[timeline left(wormhole-docs/.snippets/text/build/transfers/ntt/ntt-deployment-process-timeline.json)]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, post-deployment steps are applicable to both coding and launchpad. Maybe this section should be before Quickstart just so users can understand what the process normally looks like and then say launchpad makes it easy no installation required - not sure cause I also see the value in having quickstart be at the top of the page 🤷‍♀️

I'm not sure the descriptions should be so heavily focused on the guides, rather than the actions the guides enable you to perform. I also think the headers should be action-oriented 🤷‍♀️ 🤷‍♀️


---

Find information on configuring NTT, including guidance on setting Owner and Pauser access control roles and management of rate-limiting.
This page provides a comprehensive list of available NTT CLI commands, their descriptions, and examples to help you interact with and configure the NTT system effectively.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If users are just landing on the NTT index page and get to here, they might have questions like what is the NTT CLI and why is it relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A1 - Maintenance Major Pull request contains major updates to an existing page (i.e., adding a new section, reorgs, etc.) B0 - Needs Review Pull request is ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants