What Is a Public Key and How Does It Relate to a Wallet Address?

Updated July 13, 2026 7 min read

A crypto wallet involves three related pieces of information — a private key, a public key, and an address — and mixing up what each one does is one of the more common sources of confusion for people new to the space.

The short answer

A public key is mathematically generated from a private key using a one-way function: easy to compute in one direction, effectively impossible to reverse. The wallet address that gets shared with others isn’t the public key itself, though. It’s a further-processed, shortened version of it, created by running the public key through one or more hashing functions and adding a checksum to catch typing errors.

Why keys come in pairs

Wallets rely on asymmetric cryptography, a system built around two mathematically linked keys that do different jobs. The private key signs transactions, proving control over the funds without ever being revealed. The public key lets anyone verify that a signature was genuinely produced by the matching private key. This pairing is what lets a transaction be authenticated publicly while the actual secret — the private key — never has to leave the device that holds it. Losing sight of which key does which job is easy, which is why understanding the difference between a public address and a private key is often the first real hurdle for someone new to self-custody.

From public key to wallet address

The address most people recognize and share isn’t a raw public key. It’s typically the output of passing the public key through a hashing algorithm, then encoding the result in a format that’s shorter and includes a built-in checksum. That checksum exists specifically to catch mistakes — if a single character in an address is mistyped, the checksum generally won’t match, and many wallets will flag the address as invalid before funds are sent. This extra layer of processing is also why double-checking a wallet address before sending still matters: the checksum catches simple typos, but it can’t catch a correctly formatted address that’s simply the wrong one.

Why the address isn’t just a shortcut

Hashing the public key down into an address isn’t only about convenience. A shorter, checksummed string is easier to read, copy, and verify by eye than a long cryptographic key, which reduces the odds of a costly manual error. It also means the full public key associated with a given amount of funds isn’t necessarily exposed until those funds are actually spent, adding a layer of indirection between what’s publicly visible on the network at rest and the underlying cryptographic material.

What this means for everyday use

Hardware wallets are one common way people try to reduce private key risk, since they’re built to generate and store the private key on an isolated device that never exposes it to an internet-connected computer, a design covered in more detail when looking at how hardware wallets keep private keys offline.

The takeaway

A private key, a public key, and a wallet address form a chain: one generates the next through irreversible math, and each step trades some directness for security or convenience. Understanding that chain doesn’t require understanding the underlying cryptography in full, but it does explain why some information is safe to broadcast to the world and other information can never be shared at all — and why the consequences of mixing those two up are typically permanent.