BR Academy
Intro to Blockchain: How It Works and Why It Matters
0%
Exit course
Keys, Wallets, and Ownership·Lesson 9 of 25·12 min

Public and Private Keys

The Concept

Ownership on a blockchain isn't enforced by a login and password sitting in some company's database — it's enforced by math. Every wallet is built on a key pair: a private key, which is a secret, randomly generated number only you possess, and a public key, which is mathematically derived from that private key using one-way cryptographic functions. "One-way" is the important part: it's computationally easy to go from private key to public key, but effectively impossible to reverse the process and recover a private key from a public key, no matter how much computing power you throw at it.

This asymmetry is what makes the whole system work without a central authority. Your private key lets you produce a digital signature over any message — in practice, a transaction saying "send this amount to that address." Anyone in the world can take your public key and your signature and mathematically verify that the signature really was produced by the matching private key, without that verification ever requiring you to reveal the private key itself. It's the cryptographic equivalent of being able to prove you know a secret password without ever saying the password out loud.

From your public key, a shorter, more shareable address is derived (covered in detail in the next module) — think of the public key as your full legal signature and the address as the short account number everyone actually uses day to day.

This is also why "not your keys, not your coins" is the first rule every crypto user learns. When you hold an exchange account instead of your own private key, the exchange is the one who can produce valid signatures for your funds — you're trusting their internal database the same way you'd trust a bank, which defeats the point of a system designed to remove that trust requirement in the first place.

It helps to compare this to the systems you already trust. A bank login proves you know a password that a central server checks against its own stored copy — if that server is breached, every password it holds is compromised at once, and the bank can still freeze or reverse your transfer unilaterally because it is the final authority over its own ledger. A blockchain key pair flips both of those properties: there is no central server holding a master list of private keys to breach, and no administrator sitting above the protocol with the power to reverse a validly signed transaction. The trade-off is that the safety net disappears along with the central authority — there is no "forgot password" flow, because there is no company on the other end who could reset it for you even if they wanted to.

It's also worth being precise about what "public" means here. Your public key (and the address derived from it) can be published anywhere — on an invoice, in a tweet, on a business card — with zero loss of security, because nothing about seeing a public key helps anyone derive the matching private key. This is fundamentally different from, say, a PIN or password, where mere exposure is the entire attack. In public-key cryptography, exposure of the public half is expected and harmless; only the private half must ever remain secret.

Worked Example

Walk through what actually happens when you send a transaction:

  1. You create a transaction: "send 0.1 BTC from my address to my friend's address."
  2. Your wallet software uses your private key to produce a signature — a unique block of data mathematically tied to both your private key and this specific transaction's contents.
  3. You broadcast the transaction plus the signature (never the private key) to the network.
  4. Every node that receives it runs a verification check: using your public key (which is public, or derivable from information in the transaction), does this signature actually match this transaction? If yes, the network accepts that you — and only you — authorized it.
  5. If even one character of the transaction changed after signing (a different amount, a different recipient), the signature would no longer match, and every node would reject it instantly.

Notice what never happens anywhere in this flow: your private key never leaves your device, never gets transmitted, and never gets seen by the network. That's the entire point — proof of authorization without disclosure of the secret.

Exercise

Write one sentence explaining, to a non-technical friend, why losing your private key means losing your funds forever — with no "forgot password" link to click. Then write a second sentence explaining why, conversely, someone else obtaining your private key means they can spend your funds with no way for you to stop them, even though they never "hacked" anything — they simply gained the one piece of information the system treats as proof of ownership. Compare your two sentences: do they both make clear that the private key itself, not any company or login, is the entire security boundary?

Common Misconception

A lot of newcomers assume "signing" a transaction means something like an encrypted message gets sent — as if the private key scrambles the data itself. It doesn't. The transaction data stays fully readable to anyone; the signature is a separate, additional piece of proof bolted on alongside it. Confusing signing with encryption is one of the most common sources of confusion in this topic, so it's worth holding onto the distinction: encryption hides content, signing proves authorship. Blockchains almost never need the former, but they always need the latter.

Recap

  • A private key is a secret number that produces signatures; a public key, derived one-way from it, lets anyone verify those signatures without ever seeing the secret.
  • Signing proves authorization without revealing the private key — the whole system runs on this asymmetry, and publishing your public key or address is always safe.
  • Control of the private key is the entire ownership model: no key, no recovery, no central authority to appeal to.

Resources

← Why Blockchain Is Immutable Types of Wallets →