From 696dac6508f73f35c8565a0867e545c3ed225dfc Mon Sep 17 00:00:00 2001 From: evgenidefi Date: Thu, 19 Dec 2024 14:01:25 +0100 Subject: [PATCH] remove misleading comment about ntt program id in ntt solana deployment docs --- .../deployment-process/deploy-to-solana.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md index 977c7630..40434275 100644 --- a/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md +++ b/build/contract-integrations/native-token-transfers/deployment-process/deploy-to-solana.md @@ -112,7 +112,7 @@ This script will output the derived PDA, which you will use in the next step. ### Set SPL Token Mint Authority -In this step, you'll set SPL token mint authority to the newly generated token authority PDA: +If deploying in `burning` mode, you'll set the SPL token mint authority to the newly generated token authority PDA: ```bash spl-token authorize INSERT_TOKEN_ADDRESS mint INSERT_DERIVED_PDA @@ -121,7 +121,6 @@ spl-token authorize INSERT_TOKEN_ADDRESS mint INSERT_DERIVED_PDA !!! note Please ensure that you are using Anchor CLI version `0.29.0`. Running the deployment with a different version may cause compatibility issues. -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