Practical overview
When it fits
Use it when you want to configure and run a project for Solana SPL token creation, with liquidity-pool creation also described by the repository.
Who it is for
- Developers who want to fork and configure a Solana token-creation website.
- Operators exploring a self-hosted token creation and liquidity-pool workflow.
Documented uses
- Create Solana SPL tokens through a configured web application.
- Set up Pinata-backed IPFS storage for token metadata.
- Configure an operator fee recipient and fee values.
- Prepare a local or Vercel deployment using the repository’s documented setup.
Requirements & limits
The repository is public and provides fork-or-clone instructions. Its README documents Helius and Pinata account setup, local startup and Vercel deployment; it does not establish the access requirements or terms of a separate hosted service.
- The documented metadata-storage setup uses Pinata API keys.
- The README exposes an RPC URL setting; replacing the provider is marked Likely compatible, without provider compatibility tests.
- The README warns that the project is educational and not intended for production.
- Fee settings include a recipient, optional price, base fee and copy price.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure the token-creation website
Prepare the project configuration for a Solana RPC connection and Pinata-backed IPFS storage.
Before you start
- A fork or clone of the repository.
- A Helius account and RPC URL, as specified in the README.
- A Pinata account and API keys.
- Values for the fee recipient and any fee settings you choose to configure.
Steps
Fork or clone the repository.
Create a Helius account and obtain an RPC URL; create a Pinata account and API keys.
Open config.js and set window.rpc, window.pinata_api_key and window.pinata_secret_api_key.
Set window.recipient and any applicable fee values, including window.price, window.base_fee and window.copy_price.
Expected outcome
The project’s documented configuration values are set for RPC access, IPFS storage and operator-defined fee settings.
Guide limitations
- The README describes this project as educational and not intended for production.
- Configuration does not verify RPC-provider compatibility or establish successful token creation or deployment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- nitelin/solana-token-creator-website · Official homepage title · retained in its source language

