Deploy to Solana
Install Dependencies
Ensure you have the following dependencies installed:
Deploy NTT
Create a new NTT project (or use an existing NTT project):
Initialize a new deployment.json
file, specifying the network.
Deploy your Solana Token
If you haven't already, deploy a token to Solana.
NTT versions >=v2.0.0+solana
support SPL tokens with transfer hooks.
Generate NTT Program Keypair
When you deploy a Solana program, you need to hardcode the program ID (which is itself a pubkey) into the program code. The NTT CLI allows you to do this seamlessly.
Generate a new NTT program keypair using:
Derive the 'token-authority' PDA of the newly generated NTT Program id
Set SPL token Mint Authority to newly generated 'token authority' PDA
If deploying to Solana in burning
mode, set the mint authority for your SPL token to the NTT program ID you generated in the previous step.
Deploy NTT
Generate or export your payer keypair, then run:
The NTT Solana program will then compile and deploy.
Configure NTT
The NTT CLI takes inspiration from git. You can run:
ntt status
to check whether yourdeployment.json
file is consistent with what's actually on-chainntt pull
to sync yourdeployment.json
file with the on-chain configuration and set up rate limits with the appropriate number of decimals, depending on the specific chain. For example:For Solana, the limits are set with 9 decimal places:
For Sepolia (Ethereum testnet), the limits are set with 18 decimal places:
This initial configuration ensures that the rate limits are correctly represented for each chain's token precision
Push deployment to Solana, specifying the Keypair that will cover the gas fees
By default, NTT transfers to Solana support manual relaying, which requires the user to perform a transaction on Solana to complete the transfer. UI components such as Wormhole Connect support this out of the box. For automatic relaying support on Solana, contact Wormhole contributors.
Last updated