Solved problems of creating SPL in the local environment of Solana

As a Solana developer, creating an SPL (Self-Minting Protocol) can be a simple process. However, I ran into an issue where neither the CLI nor the JS packages were able to build the SPL in my local environment. In this article, we will explore the possible causes of this problem and provide steps to resolve it.

Validation node is working

Before we dive into the issues of creating an SPL, let’s make sure our validator node is working properly. The validator node is responsible for validating and processing transactions on the Solana blockchain. If you are using a local instance of the validator node, you can check its status by checking the following:

• Open the solana CLI' command line tool and navigate to your project directory.

• Runsolana config get validators, which should display a list of available validator nodes.

• Verify that at least one of these nodes is listed as active.

Potential SPL Creation Issues

Assuming our validator node is up and running, let's take a look at potential SPL creation issues:

• Network Issues: The most common reason for token failures in on-premises Solana environments is network connection issues. Make sure your internet connection is stable and working properly.

• Account Limits: If your account limits are exceeded or insufficient, your transaction may fail. Check your account balance and update if necessary to avoid issues.

• Token Name and Token: The token name and token must match in the CLI package (e.g.spl-token create-token) and the JS package (e.g.import { createToken } from ‘@solana/spl-token’;). Make sure they are identical.

Troubleshooting Procedure

To resolve this issue, try the following:

• Check your network connection: Make sure your internet connection is stable and working properly.

• Update Account Limits: Check your account balance and update if necessary to avoid exceeding your account limit.

• Check token name and symbol: Double-check that the token names and symbols in the CLI and JS packages match.

• Check transaction logs: Run the following command to view transaction logs:solana logs –json create-token`. This will help identify transaction or network connection issues.

Example of use

To illustrate this problem, let’s create a simple token minting script using both the CLI and JS packages:

// CreateToken.js
import { createToken } from '@solana/spl-token';
const account = 'YOUR account address';
const symbol = 'SPL';
createToken({ account, symbol })
.then((mint) => console.log(mint))
.catch((error) => console.error(error));

Create a token using the CLI package (spl-token create-token)
spl-token create-token --account  --symbol 

// CreateToken.js (using the CLI)
import { createToken } from '@solana/spl-token';
const account = 'YOUR account address';
const symbol = 'SPL';
createToken({ account, symbol })
.then((mint) => console.log(mint))
.catch((error) => console.error(error));

By following these troubleshooting steps and checking for the potential issues listed above, you should be able to resolve any issues you encounter while creating SPL in your local Solana environment.