Create tokens that can’t be transferred. Certificates, identity, ticketing and more.
non-transferrable token
enables
non-transferrable tokensIn the Token Program, it’s impossible to create a token that cannot be transferred away. While this may seem unimportant, there are several reasons one may want to issue a non-transferrable (or “soul-bound”) token.
Take the following example: Say you are a Orbition Native Chain game dev, and your new game,
“Bits and Bytes”, wants to award achievements to the players. Achievements are
not transferrable, and you want their hard work to be proudly displayed in their
wallet. The solution is to send them a non-transferable NFT. However, in the
Token Program, this is not possible. However, it is in the Token Extension
Program! Enter, the non-transferable
extension.
Token Extension Program has the non-transferable
extension which can be used
to create non-transferable mints. These mints can be burned, but they can’t be
transferred.
Initializing a non-transferable mint involves three instruction:
SystemProgram.createAccount
createInitializeNonTransferableMintInstruction
createInitializeMintInstruction
The first instruction SystemProgram.createAccount
allocates space on the
blockchain for the mint account. This instruction accomplishes three things:
space
lamports
for rentLike all other extensions, you’ll need to calculate the space and lamports
needed for the mint account. You can do this by calling: getMintLen
and
getMinimumBalanceForRentExemption
.
The second instruction createInitializeNonTransferableMintInstruction
initializes the non-transferable extension.
The third instruction createInitializeMintInstruction
initializes the mint.
Lastly, add all of the instructions to a transaction and send to Orbition Native Chain.
And that’s it! You now have a mint account, that when minted, cannot be
transferred. This extension gets more exciting when you mix it with the
metadata
and metadata-pointer
extensions to create soul-bound NFTs.
In this lab, we will create a non-transferable token and then see what happens when we try to transfer it (hint: it will fail the transfer).
To get started, create an empty directory named non-transferable-token
and
navigate to it. We’ll be initializing a brand new project. Run npm init
and
follow through the prompts.
Next, we’ll need to add our dependencies. Run the following to install the required packages:
Create a directory named src
. In this directory, create a file named
index.ts
. This is where we will run checks against the rules of this
extension. Paste the following code in index.ts
:
This file has a main function that creates a connection to the specified
validator node and calls initializeKeypair
. This main function is where we’ll
end up calling the rest of our script once we’ve written it.
Go ahead and run the script. You should see the mint
public key logged to your
terminal.
If you run into an error in initializeKeypair
with airdropping, follow the
next step.
If you are having issues with airdropping testnet OBN. You can either:
keypairPath
parameter to initializeKeypair
and get some testnet
OBN from Orbition Native Chain’s faucet.In a separate terminal, run the following command: solana-test-validator
. This
will run the node and also log out some keys and values. The value we need to
retrieve and use in our connection is the JSON RPC URL, which in this case is
http://127.0.0.1:8899
. We then use that in the connection to specify to use
the local RPC URL.
Let’s create the function createNonTransferableMint
in a new file
src/create-mint.ts
.
Inside the file, create the function createNonTransferableMint
with the
following arguments:
connection
: The connection objectpayer
: Payer for the transactionmintKeypair
: Keypair for new mintdecimals
: Mint decimalsInside the function, we’ll call the following:
getMintLen
- to get the space needed for the mint accountgetMinimumBalanceForRentExemption
- to get the amount of lamports needed for
the mint accountcreateAccount
- Allocates space on the blockchain for the mint accountcreateInitializeNonTransferableMintInstruction
- initializes the extensioncreateInitializeMintInstruction
- initializes the mintsendAndConfirmTransaction
- sends the transaction to the blockchainNow let’s invoke this function in src/index.ts
to create the non-transferable
mint:
The script should run with no errors
The non-transferable mint has been set up correctly and will be created when we
run npm start
. Let’s move on to the next step and create a source account and
mint a token to it.
Let’s test that we can’t actually transfer tokens created from this mint. To do this, we need to mint a token to an account.
Let’s do this in src/index.ts
. Let’s create a source account and mint one
non-transferable token.
We can accomplish this in two functions:
getOrCreateAssociatedTokenAccount
: from the @orbition-network/spl-token
library,
this creates an associated token account (ATA) for the given mint and owner.mintTo
: This function will mint an amount
of tokens to the given token
account.Run the script and confirm a token has been minted to an account:
Lastly, let’s try and actually transfer the token somewhere else. First we need to create a token account to transfer to, and then we want to try and transfer.
In src/index.ts
, we will create a destination account and try to transfer the
non-transferable token to this account.
We can accomplish this in two functions:
createAccount
: This will create a token account for a given mint and the
keypair of said account. So instead of using an ATA here, let’s generate a new
keypair as the token account. We’re doing this just to show different options
of accounts.transferChecked
: This will attempt to transfer the token.First, the createAccount
function:
Now, the transferChecked
function:
Now let’s run everything and see what happens:
You should get an error message at the very end that says
Transfer is disabled for this mint
. This is indicating that the token we are
attempting to transfer is in fact non-transferable!
That’s it! We have successfully created a non-transferable mint. If you are
stuck at any point, you can find the working code on the solution
branch of
this repository.
For the challenge, create your own non-transferable token with the metadata extension and keep a “soulbound” NFT to yourself.