If you’ve ever run ssh-keygen to push code to GitHub or access a remote server, you already understand 90% of how identity works on Solana.

In the Web2 world, "identity" is usually something a company lends to you. You have a row in a PostgreSQL database owned by Google or Meta. If they delete that row, your identity vanishes. In the Web3 world—specifically on Solana—identity is something you math into existence.

Here is how we move from "Login with Google" to "Login with Cryptography."

1. The Keypair: Your Global Passport

In Web2, your identity is a Username + Password stored on a centralized server. On Solana, your identity is a Keypair.

A keypair consists of two parts:

• The Public Key (Your Address): Think of this like your IBAN (International Bank Account Number) or your email address. You share this with the world so people know where to send SOL or tokens.

• The Private Key (Your Signature): This is your "password," but it’s never stored on a server. It stays on your machine (or in your wallet).

When you "log in" to a Solana app, you aren't sending a password to be checked against a database. Instead, you are using your private key to digitally sign a piece of data. The network uses your public key to verify that signature. If the math checks out, you are who you say you are.

N/B: We use a private key to sign transactions (such as sending crypto or messages), while the public key is used to verify those transactions and receive funds.

2. Accounts: The Folders of the Network

On Solana, everything is an Account. If the Solana blockchain is a giant global operating system, accounts are the files.
In Web2, a database might have a users table with columns for balance, username, and profile_pic. On Solana, your public key points to an account on the network that stores:

• Lamports: The smallest unit of SOL (named after Leslie Lamport). 1 SOL = 1,000,000,000 lamports.
• Owner: The program (smart contract) that is allowed to change the account's data.
• Data: A buffer of bytes where information (like your token balances) is stored.

3. Ownership vs. Permission

The biggest "click" moment for a Web2 developer is realizing there is no "Forgot Password" button.

• In Web2: You own your account because a company grants you access. They can lock you out or reset your password.
• In Web3: You own your account because you hold the private key. Because the network is decentralized, no one—not even the creators of Solana—can "admin" your account.

During my first week diving into Solana, I realized that managing these keys manually is risky. That’s where the "Wallet" comes in. Tools like Phantom (a browser wallet) act as a "Identity Proxy." They hold your private keys securely and provide a UI for you to "Sign" transactions when a web app requests it.

Summary

Identity on Solana isn't a record in a company's database; it’s a cryptographic proof. It’s self-custodied, meaning you are the sole gatekeeper of your digital presence.

If you're coming from a Web2 background, stop thinking about "Accounts" as entries in a table and start thinking about them as cryptographically secured files that only you have the key to edit.