Native Token Transfers Post Deployment＃
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):
- Implement a robust testing plan for your multichain token before launching
- Ensure comprehensive, documented security measures are followed for custody of contract ownership, control of keys, and access control roles. Check the NTT configuration for more details on ownership and rate limits
- Consider a streamlined, customizable frontend such as Wormhole Connect for an optimized user experience
- Alternatively, the Wormhole TypeScript SDK allows for a direct integration into your infrastructure
- 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
- Monitor and maintain your multichain deployment
Manual Relaying for Solana Transfers＃
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.
This step ensures that tokens are properly minted or unlocked on Solana and prevents unauthorized claims.
Wormhole Connect support this process automatically.
Where to Go Next＃
-
Wormhole NTT Connect Demo
Check out an example project that uses a Vite-React TypeScript application and integrates it with Wormhole Connect, a customizable widget for cross-chain asset transfers.
-
Wormhole NTT TypeScript SDK Demo
Reference an example project that uses the Wormhole TypeScript SDK to facilitate token transfers between different blockchain networks after deploying the NTT framework.