Forem: Hope

I Built a Token System on Solana (Without Any Backend Code)

Hope — Mon, 25 May 2026 03:37:30 +0000

If you told me a week ago that I could create a custom currency, add brand metadata, enforce automatic transaction fees, and create "soulbound" non-transferable credentials—all without writing a single line of backend API code—I would have been skeptical.

Coming from a Web2 background, my brain is wired to think in APIs, Databases, and Middleware.

But over the last few days, I’ve been building on Solana using the Token Extensions (Token-2022) Program, and it has completely changed how I think about building apps.

The Web2 Way vs. The Solana Way

In a traditional web app, if I wanted to launch a "Reward Coin" system, I’d have to:

Build a database table to store balances.
Write an API endpoint to check if a user has enough coins.
Write a tax-collection service to skim fees off transfers.
Add security checks to make sure users can't edit the database themselves.

On Solana, the protocol handles the heavy lifting.

My Token-Building Journey

This week, I walked through the full lifecycle of token design. Here is what I learned about these three "superpowers" of Solana tokens:

1. Metadata: Tokens with an Identity

A token without metadata is just a nameless string of characters. Using spl-token initialize-metadata, I attached a name, symbol, and image link directly to my token mint.

The Lesson: You aren't just storing a number; you are attaching an identity to an asset that lives on-chain forever.

2. Transfer Fees: Protocol-Level Revenue

This was the most eye-opening part. I created a token with a built-in 2% transfer fee.

The Why: In Web2, I’d need a complex payment processor. Here, I just set a --transfer-fee parameter. When a user sends 100 tokens, the program automatically withholds 2 tokens in a locked state, and I can sweep them into my treasury whenever I want.
The Surprise: The blockchain rejects any transaction that doesn't account for the fee. The security is enforced by the math, not by my backend code.

3. Non-Transferable Tokens: The "Soulbound" Credential

Finally, I experimented with the --enable-non-transferable flag. This creates a token that is permanently "stuck" to the wallet that receives it.

Use Case: Think of course certificates, membership badges, or employee IDs.
The Proof: I literally tried to send these tokens to a second wallet, and the Solana network threw a Transfer is disabled error. It wasn't my code failing; it was the blockchain itself saying "No."

What Surprised Me Most

The biggest hurdle was the "Decimal Math." When you set your token to 9 decimals, everything is calculated in "base units." I hit a few errors where my expected fee didn't match the program's calculation because I was thinking in whole numbers rather than the token's smallest unit. Once I understood that the program was calculating the exact math, the errors disappeared.

What’s Next?

Moving from "I can send SOL" to "I can define the economic rules of an asset" feels like a huge level-up.

If you are a developer looking to get into Web3, don't just read the docs—start by building a token. It forces you to understand account ownership, rent, and data storage faster than any tutorial ever could.

I’m excited to keep building. Next up, I’m looking into how to connect these tokens to a frontend dashboard. If you're also learning Solana, let’s connect!

Solana Accounts Explained to a Web2 Developer

Hope — Fri, 22 May 2026 14:56:09 +0000

If you are coming from a traditional Web2 background (like building with Node.js, databases, or cloud servers), your first look at a blockchain can be confusing. You hear terms like smart contracts and state transition, but how does data get saved?

On Solana, Everything is a file.

Well, Solana calls them Accounts, but they act just like files in a computer operating system. Let's break down how Solana stores data using terms you already know.

1. The Big Idea: Everything is a File (Account)

In Web2, you might use a Linux server. On that server, you have executable files (programs) and data files (such as .json or .txt).

Solana works the same way. Instead of a hard drive, Solana uses a giant, flat key-value store.

The Key: A 32-byte string called a Public Key (like So11111111111111111111111111111111111111112). This is your file name or path.
The Value: The account itself. This is the actual file contents and metadata.

Whether it's a user wallet, a piece of code, a token balance, or a picture of an NFT—on Solana, it is always an account.

2. The 5 Fields Inside Every Account

Just like a file on your computer has a size, an owner, and permissions, every single Solana account contains the same five pieces of information:

Field	What it means in Web2 terms
Lamports	The bank balance of the file. A lamport is a tiny fraction of a SOL coin (1 SOL = 1 billion lamports).
Data	The actual contents of the file. A flat array of bytes where you can save any information.
Owner	The specific program (app) that is allowed to change this file's data.
Executable	A true/false switch. If true, this file is a program (code). If false, it's just data.
Rent Epoch	A background field used by the network (mostly system maintenance data).

Here is what it looks like if you inspect a real account using the Solana command line:

{
  "lamports": 2039280,
  "data": ["SGVsbG8gV29ybGQ=", "base64"],
  "owner": "11111111111111111111111111111111",
  "executable": false,
  "rent_epoch": 18446744073709551615
}

3. Programs are Stateless

This is the biggest surprise for Web2 developers.

In Web2, your app server usually holds some data in memory, or your code handles its own database connections. On Solana, programs (smart contracts) cannot store data inside themselves. They are stateless.

Think of it like this:

The Program Account: This is your compiled code. Its executable flag is set to true. It sits there like a web server application, ready to run.
The Data Account: This is your database row. Its executable flag is false.

When a user wants to interact with an app, they pass both the Program (the code) and the Data Account (the file) to the network. The program reads the data file, updates it, and saves it back.

4. The Golden Rule: App Security

How do we stop people from changing your data account and giving themselves a million tokens? Solana has a very strict security rule built into its core:

Only the program listed as the "Owner" of an account can change its data.

If Program A tries to modify a data file owned by Program B, the Solana network rejects the change. However, anyone is allowed to send money (lamports) into any account. You can deposit money into a friend's bank account, but only the bank's system can update their account status.

5. Rent: Paying for Storage Space

On a cloud platform like AWS, you pay a monthly fee to keep your files stored on a hard drive. If you stop paying, AWS deletes your files.

Solana manages storage similarly, but with a twist. To keep a file on the blockchain, the account must hold a minimum amount of SOL coins. The bigger your data file, the more SOL you need to leave in it. This is called being Rent-Exempt.

For a basic wallet account with no extra data, it costs a tiny fraction of a cent (around 0.00089 SOL) to stay on the network forever. If you ever close the account and delete the file, you get all that SOL back!

Wrapping Up

To survive and build on Solana, just remember these four rules:

Everything is a file called an account.
Code and data live in completely separate files.
Programs are stateless; they just read and write to data accounts.
Only the owner program can modify a file's data.

Once you view the blockchain as a giant, secure file system, writing applications becomes much easier to visualize!

Victory Lap

Hope — Tue, 05 May 2026 04:23:59 +0000

I’ve been diving into Solana development for the past 10+ days as part of 100DaysOfSolana.

Today, I successfully moved my scripts into the browser to build a functional Devnet Dashboard. It was a great exercise in handling RPC providers and managing BigInt data for UI display.

Major shoutout to Major League Hacking for the challenge. Looking forward to the next arc!

My Second Week Building on Solana

Hope — Sun, 03 May 2026 15:11:52 +0000

I just finished my second week of the #100DaysOfSolana challenge, and my brain feels like it’s been rewired. Coming from a traditional software background, I thought a blockchain was just a slow database. I was wrong.

The "Aha!" Moment: Everything is an Account

The biggest thing that clicked for me this week was the Account Model. In the apps I usually build, data lives in a private database (like MongoDB) and the code lives on a server. On Solana, everything—your wallet, your data, and even the "smart contract" code—is an account sitting on a giant, public ledger.

What Surprised Me

I spent today comparing Solana accounts to traditional databases. Here are the three things that shocked me most:

Public by Default: I can take my wallet address, throw it into a website like the Solana Explorer, and see every single transaction I’ve ever made. There’s no "admin password" needed to see the data—it’s just there.
Rent is Real: You actually have to pay a small "security deposit" in SOL to store data on the blockchain. If you want to store more bytes, you pay more. The cool part? If you delete the data, you get your money back.
The "Ghost" Transaction: I learned the hard way that just because a website says "Success" doesn't mean your money has arrived yet. You have to wait for the network to "finalize" the transaction.

My Terminal Adventures

I spent a lot of time in the terminal this week. One of the most satisfying moments was finally seeing my balance update after a few failed airdrops:

# Checking my "identity" on the devnet
solana account $(solana address)

# The result:
Public Key: 5bsSMz6oc4gHp5BkBFSR9HK4mn7NBTimvsgSL9soXktj
Balance: 1.5 SOL
Owner: 11111111111111111111111111111111 (System Program)
Executable: false

What's Next?

I’m still wrapping my head around how different programs talk to each other without using "JOIN" commands like in SQL. It feels like learning to walk again, but in a world where everything is transparent and decentralized.

Next week, I’m diving deeper into building dashboards that read this data in real-time!

My Wallet Experiences

Hope — Sun, 26 Apr 2026 22:29:11 +0000

What I did: This week, I went from generating raw key pairs in the terminal to building a web app that connects to browser wallets like Phantom.

What surprised me: The biggest "aha" moment was realizing that a wallet is a UI for a cryptographic key pair that serves as my universal identity.

What's next: I'm excited to move past the basics and start writing my own on-chain programs!

How Identity Actually Works on Solana

Hope — Sun, 26 Apr 2026 22:14:51 +0000

Beyond Passwords: Understanding Identity on Solana

In the Web2 world, your identity is basically a row in a database owned by someone else. You have a username for GitHub and an email for Google. You rely on these companies to hash your password, handle forgotten password emails, and keep your data safe. On Solana, there are no databases or admins. Your identity is built on the keypair.

Think of it Like an SSH Key

If you’ve ever connected to a server using an SSH key, you already understand Solana. You generate a public key and a private key. You share the public one and keep the private one hidden. To prove who you are, you use the private key to sign a request.

On Solana, the entire network is the server. Your public key is your address, and your private key is your proof of ownership. To move money or talk to a smart contract, you just sign the request with that private key.

Why Addresses Look So Weird

Instead of a username, a Solana address looks like a long string of random characters. This string is encoded in Base58.

Solana uses Base58 to prevent human errors. It removes confusing characters that look alike, such as:

The number zero (0)
The capital letter O
The capital letter I
The lowercase letter l

This makes it much harder to make a mistake when you are copying or reading an address.

You Are the Only Boss

In Web2, a company can lock your account or get hacked. They own your data. You just have permission to use it. On Solana, ownership is cryptographic. Only the person holding the private key can make changes.

There is no password reset button. If you lose your private key, you lose your account forever. While that sounds scary, it also means no company or admin can ever block you or take your funds. You are in total control.

One Key for Everything

Because your identity is based on math, it works everywhere. You just connect your wallet, and every game, marketplace, or exchange on the network instantly knows it's you. It’s like having a universal passport that works across the entire internet without needing anyone's permission.