Qaynaq LABS · TOOLS

CRYPTO GLOSSARY

Public key

A cryptographic key that can be shared openly and is used to receive or verify transactions, while keeping the corresponding private key secret.

Technical definition

In public-key cryptography, a public key is a large numerical value derived from a private key using a one-way mathematical function (e.g., elliptic curve multiplication or modular exponentiation). It serves as an address or identifier in blockchain systems, allowing others to send assets or verify digital signatures without exposing the private key. Public keys are typically represented in compressed or uncompressed formats (e.g., hexadecimal, Base58, or Bech32) and are computationally infeasible to reverse-engineer into the private key due to the properties of the underlying cryptographic algorithm.

An analogy

Imagine a public key as a mailbox address: anyone can see it and use it to send you mail (or cryptocurrency), but only you, with the private key (like a mailbox key), can open the mailbox and access the contents.

Why it matters

Public keys enable secure, trustless interactions in decentralized systems by allowing parties to verify identities and transactions without sharing sensitive information. They are fundamental to digital signatures, encryption, and blockchain address generation.

Where it came from

Public-key cryptography was introduced by Whitfield Diffie and Martin Hellman in 1976, building on earlier work by Ralph Merkle and others. Its application in blockchain systems, particularly Bitcoin (2009), popularized the use of public keys as addresses for transactions.

Example in practice

In Bitcoin, a user’s public key is derived from their private key and hashed to create a public address (e.g., 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa). Others can send Bitcoin to this address, and the user can later spend it by proving ownership with the corresponding private key.

Common misconceptions

  • A public key is the same as a wallet address → Correction: A wallet address is typically a hashed version of the public key, often with additional checksums or encoding for usability.
  • Public keys are secret → Correction: Public keys are designed to be shared openly; their security relies on the private key remaining undisclosed.
  • Public keys can be used to spend funds → Correction: Only the private key can authorize transactions; the public key is used to verify signatures.

Risks & limitations

  • Loss of funds if the private key is compromised (even if the public key is exposed).
  • Quantum computing advances could theoretically weaken public-key cryptography (e.g., Shor’s algorithm breaking ECC or RSA).
  • Public keys linked to identities (e.g., via metadata or reuse) may expose users to surveillance or targeted attacks.
  • Weak randomness in key generation can lead to predictable private keys, making funds vulnerable to theft.

Related terms

About "Public key" in crypto

Cryptocurrency vocabulary moves faster than any other technical field. New terms appear weekly, old terms quietly change meaning, and most "definitions" online were written by someone trying to sell you something. Qaynaq Labs' crypto glossary aims for the opposite: neutral, accurate, skeptical explainers that include the downside.

This entry covers the technical mechanics, a real-world analogy, where the concept came from, and what could go wrong. Pair it with the related terms to build a working mental model of how the pieces fit together.

Frequently asked

Can someone steal my cryptocurrency if they know my public key?

No. While a public key can be used to receive funds, spending or transferring those funds requires the corresponding private key, which must remain secret.

Why do some blockchains use different formats for public keys (e.g., compressed vs. uncompressed)?

Different formats optimize for storage efficiency (compressed keys use fewer bytes) or compatibility with specific address schemes. Compressed keys are derived by adding a prefix to the public key before hashing.

How are public keys generated from private keys?

In Bitcoin and many other systems, a private key (a random 256-bit number) is multiplied by a generator point on the secp256k1 elliptic curve to produce a public key, which is a point on the curve represented as (x, y) coordinates.

Are public keys always the same length?

No. The length depends on the cryptographic algorithm used. For example, Bitcoin’s secp256k1 public keys are 65 bytes (uncompressed) or 33 bytes (compressed), while Ethereum uses 64-byte public keys derived from secp256k1.