Week1 of #100DaysOfSolana: Understanding Identity on Solana (A Simple Guide for Web2 Developers)

Peter Okoh — Mon, 04 May 2026 11:28:14 +0000

If you’re coming from Web2, identity probably means a username and password. You sign up for a service, create credentials, and the platform stores your data. Whether it’s GitHub, your email, or a banking app, your identity exists because a company manages it.

Solana works differently.

On Solana, your identity starts with something called a keypair. This is made up of two things: a public key and a private key.

Think of the public key as your username (or wallet address) and the private key as your password, but much more powerful. Instead of typing your password, you use your private key to cryptographically sign actions. That’s how you prove ownership.

A helpful way to understand this is through SSH keys. If you’ve ever connected to a server using SSH, you know you don’t always use a password. Instead, you generate a keypair, put the public key on the server, and keep the private key on your machine. When you connect, the server checks if you can prove you own the private key. If you can, you’re in.

Solana works in a very similar way, except the “server” is the entire network.

One big difference from Web2 is that there are no usernames or centralised accounts. Your identity looks like a long string of characters (your public key), and you generate it yourself. No company approves it or stores it for you. That means your identity isn’t tied to any single platform; it works across every app built on Solana.

Another important shift is ownership. In Web2, you don’t fully own your account. A company does. They can suspend you, reset your password, or restrict access. On Solana, ownership is purely based on who controls the private key. If you have it, you have full control. If you lose it, there’s no “forgot password” option. That responsibility is entirely yours.

This might sound risky, but it also unlocks something powerful. Your identity becomes portable. The same keypair you use to hold tokens can also be used to interact with apps, vote in governance systems, or build a reputation. You don’t need to create a new account for every platform. You just connect your wallet and go.

From a developer’s perspective, this changes how you think about users. You’re no longer managing accounts with emails and passwords. Instead, users bring their own identity (their wallet), and your app interacts with it. Authentication becomes “sign this message” instead of “enter your password".

Of course, there are tradeoffs. Managing private keys safely is critical. That’s why there are different wallet types, CLI wallets for development, browser wallets for everyday use, and mobile or hardware wallets for better security. They all manage the same keypair but in different ways.

At its core, identity on Solana is simple: you are your keypair. There’s no middleman, no centralised control, and no dependency on a single platform. Once you understand that, the rest of the ecosystem starts to make a lot more sense.

I am happy to be sharing, and I anticipate your thoughts.

DEV Community: Peter Okoh

Week1 of #100DaysOfSolana: Understanding Identity on Solana (A Simple Guide for Web2 Developers)

100DaysOfSolana