Understanding Identity on Solana as a Web2 Developer

Ajiri Osiobe — Tue, 12 May 2026 21:13:12 +0000

Its day 6 of the 100-days-of-solana event hosted by the MLH community.

First of all, I joined late, they are currently on Day 23, my job is to play catch.

For the past 5 days, one concept kept coming up everywhere: keypairs. Wallets, transactions, accounts, signatures — almost everything seemed to revolve around them.

Coming from a Web2 background as a fullstack developer, this felt confusing at first. In Web2, identity usually means usernames, emails, passwords, sessions, OAuth, or JWT tokens. On Solana, identity works very differently.

The breakthrough for me came when I stopped thinking about wallets as “bank accounts” and started thinking about them like SSH keys.

Identity in Web2

In traditional applications, identity is usually controlled by a company or platform.

For example, when you create a GitHub account:

GitHub stores your username and password
GitHub decides whether your account exists
GitHub can reset your password
GitHub can suspend or delete your access

Your identity depends on a centralized database.

Even when using OAuth providers like Google Sign-In, your identity still depends on another company managing credentials and permissions.

This model works well, but it also means users do not fully control their identity.

Solana Identity Feels Like SSH Keys

If you have ever used SSH to connect to a server, Solana becomes much easier to understand.

With SSH:

You generate a public and private keypair
The public key goes on the server
The private key stays with you
You prove ownership by signing requests with your private key

Solana works almost the same way.

When you create a Solana wallet, you generate:

A public key → your wallet address
A private key → your proof of ownership

Your public key becomes your identity on the network.

Instead of logging into a single server, your identity is recognized across the entire Solana blockchain.

What Is a Solana Address?

A Solana address is actually a public key.

It is a 32-byte Ed25519 public key encoded in Base58, which produces addresses like this:

14grJpemFaf88c8tiVb77W7TYg2W3ir6pfkKz3YjhhZ5

Base58 is intentionally designed to avoid confusing characters like:

0 and O
I and l

This reduces mistakes when copying addresses.

Unlike a username in Web2, nobody “assigns” you this identity. It is mathematically generated and cryptographically tied to your private key.

Ownership Without Permission

One of my biggest mindset shifts learning Web3 is understanding ownership.

In Web2, companies grant access to your account.

In Solana, cryptography proves ownership directly.

If you hold the private key, you control the account.

That means:

No admin can freeze your identity
No password reset exists
No centralized authority controls access

The network only trusts cryptographic signatures.

When you send a transaction on Solana, your wallet signs it with your private key. Validators verify the signature using your public key.

If the signature is valid, the network accepts the transaction.

This is why protecting your seed phrase is so important. Losing it is like losing the master key to your identity.

Identity Beyond Wallets

At first, I assumed wallets were only for storing tokens.

But identity on Solana enables much more:

Owning tokens and NFTs
Interacting with programs (smart contracts)
Participating in governance votes
Building on-chain reputation
Logging into decentralized applications

What makes this powerful is portability.

In Web2, every application creates its own identity system.

In Solana, the same identity works across the entire ecosystem.

You do not create separate accounts for every app. Your wallet becomes your universal identity layer.

Browser Wallets vs CLI Wallets

Over the past few days, I experimented with both browser wallets and the Solana CLI wallet.

The browser wallet felt easiest for interacting with decentralized apps because it handles signatures visually and connects quickly.

The CLI wallet felt more developer-focused and secure because it gives direct control over keys, accounts, and transactions from the terminal.

Using both helped me understand that wallets are not just storage tools — they are interfaces for managing cryptographic identity.

Final Thoughts

The biggest lesson for me is that identity on Solana is self-custodied.

In Web2, platforms own the identity layer.

In Solana, users own it themselves through cryptography.

That changes how authentication, ownership, and trust work on the internet.

For a Web2 developer, the easiest way to understand Solana identity is this:

A Solana wallet is basically your SSH key for the blockchain.

Except instead of authenticating with one server, you are authenticating with an entire decentralized network.

100daysofsolana #solana #web3 # blockchain #beginners

DEV Community: Ajiri Osiobe