What Is a Public Key in Crypto?

How do the two keys work together?

Every crypto account is a key pair created together by the wallet’s mathematics. The private key signs transactions; the public key lets the network verify those signatures without ever seeing the private one. It’s the same idea as a locked mailbox: the slot (public) accepts letters from anyone, the key (private) opens it. Deriving works one way only — private → public — which is why you can publish the public half to the entire world without weakening the lock.

This asymmetry is the load-bearing wall of the whole system. When you send a transaction, your wallet attaches a signature produced with the private key; every node on the network checks it against the public key and rejects anything forged. Thousands of independent computers verify your authority to spend without ever learning the secret that grants it — that is the trick blockchain accounts are built on.

Is your public key really safe to share?

Yes — that’s its whole purpose. It becomes your receiving address, printed on invoices and donation pages everywhere. Two practical notes: sharing an address reveals your transaction history and balance for that address, which is why privacy-conscious users generate a fresh address per payment (wallets do this automatically). And while sharing is safe, transcribing is where errors happen — one wrong character and the money goes to a void address nobody can reclaim. Use copy-paste or QR codes, and when moving serious amounts, send a small test transaction first, the way our deposit guide recommends.

The full key hierarchy, in one picture

Beginners conflate three levels, and scammers exploit the confusion:

1. Address — bc1q… or 0x…. What you share. Derived from the public key. Safe to publish, reveals your on-chain history.
2. Private key — controls one account. Derived from the phrase. Never share, never photograph.
3. Seed phrase — 12–24 words. The master backup from which all private keys are generated. The crown jewels; see the storage rules.

Losing the first is an inconvenience. Leaking the third is total loss, and “total” is literal — restore the words on any device anywhere in the world and everything is gone. Our private keys guide walks the full hierarchy with worked examples of how a signature gets verified.

How a transaction actually gets verified

Watching the mechanism once makes the whole key model click. Say you send 0.1 BTC:

1. Build. Your wallet assembles the transaction: amount, destination address, fee — an unsigned letter.
2. Sign. Your private key generates a mathematical signature over that exact transaction. The signature proves the holder of the key approved this transaction — change one character of it and the signature stops being valid.
3. Broadcast. The signed transaction hits the network. Importantly, the private key itself stays on your device; only the signature travels.
4. Verify. Every node takes the signature, the transaction, and your public key and runs the check: does this signature match this data with this key? Forged signatures fail the math; there is no way to fake one without the private key.
5. Record. Valid transactions get packaged into a block, and the transfer is permanently public — visible to anyone via your address, forever.

The elegant part: thousands of unrelated computers worldwide verified your authority to spend without ever learning the secret that grants it. That verification dance — public keys prove identity, private keys prove intent — is the load-bearing trick of the entire system, and it’s why the two key types have exactly the sharing rules they do.