From Web2 to Web3: My First Solana Tokens

aprajita singh — Sun, 24 May 2026 11:37:45 +0000

Introduction
Moving from traditional web development to blockchain can feel like entering a completely different dimension. As a student developer, I recently took the plunge into the Solana ecosystem during the #100DaysOfSolana challenge.

In just a few days, I went from knowing absolutely nothing about smart contracts to launching real tokens with built-in economic rules. Here is exactly how I did it, what I built, and the mind-blowing concepts I learned along the way.

🛠️ The Tech Stack & Setup
Before writing any code, I set up my workspace using modern cloud and blockchain tools:

Environment: Google Cloud Shell (for a seamless, zero-installation terminal experience)

Language/Runtime: Node.js & TypeScript

Version Control: GitHub (for managing repository states)

SDKs: Solana Web3.js and the @solana/spl-token library

🚀 The Core Walkthrough: Building the Token Architecture
Instead of using the old, rigid Token Program, I utilized Solana’s cutting-edge Token Extensions Program (Token-2022). This allows developers to hardcode complex financial and structural behavior directly into the token mint itself, without writing custom Rust smart contracts.

Creating the Mint with Metadata The first milestone was creating a completely customized token mint. I attached a name, symbol, and an official metadata pointer directly to the mint account.

TypeScript
import {
createMint,
token2022ProgramId,
TYPE_SIZE,
LENGTH_SIZE
} from "@solana/spl-token";

// Initializing the advanced Token-2022 Mint
const mint = await createMint(
connection,
payer,
mintAuthority,
freezeAuthority,
decimals,
keypair,
undefined,
token2022ProgramId
);
console.log(✅ Token Mint Created Successfully: ${mint.toBase58()});

Protocol-Level Transfer Fees One of the coolest aspects of Solana Token Extensions is implementing a native transfer fee. Instead of enforcing royalties or transaction taxes on a centralized website or application layer, the Solana network handles it automatically at the ledger level.

Every time a user moves the token, a fixed percentage or absolute fee is automatically deducted and sent to a designated fee authority account.

Creating "Soulbound" Permanent Credentials The journey culminated in experimenting with Non-Transferable Tokens. These are tokens that, once minted into a user's wallet, can never be transferred out or sold.

This creates a bulletproof mechanism for digital identity, permanent certifications, and credentials that exist strictly on-chain. Traditional Web2 platforms rely on heavy database policy documents to protect accounts; Solana enforces it natively through cryptographic immutability.

💡 What Surprised Me the Most
Coming from a Web2 mindset, I expected blockchain deployment to be filled with heavy boilerplate configuration and endless debugging. However, two things caught me off guard:

On-Chain vs. App Logic: In traditional development, if you want to charge a transaction fee, you write a line of code in your server (like Express or Python). On Solana, you program it directly into the money itself. The token carries its own laws wherever it goes.

The Power of Cloud Shell: Running complex Solana command-line tools and managing private keypairs directly inside Google Cloud Shell made the development phase extremely fast and lightweight.

🔮 What's Next?
Building these assets has opened my eyes to the future of decentralized applications (dApps). My next goal is to build an interactive front-end dashboard where users can view their real-time token balances and see environmental or utility logs updating live.

The Web3 space moves incredibly fast, but taking the time to document my progress ensures these lessons stick for good.

This post is part of my submission for the #100DaysOfSolana challenge. Special thanks to Major League Hacking (MLH) and the global developer community for the incredible support!

DEV Community: aprajita singh

From Web2 to Web3: My First Solana Tokens