Public Key

Overview

Why Public Key matters

A network that does not know a user's real-world identity still needs to check whether a transaction was approved by the controller of funds. Public-key cryptography solves this by separating the secret used to sign from public information used to verify. Verification does not require disclosing the private key or asking a central authority whether the user approves each transfer.

How it works

Wallet software generates a private key and mathematically derives a public key according to the network's cryptographic scheme. When the user authorizes a spend, software signs a defined message or transaction with the private key. A node checks the signature against the appropriate public key and the network's spending rules. In Bitcoin, what must be supplied depends on the output type and locking script; a receiving address often encodes a hash or another commitment rather than the complete public key. In Ethereum-style externally owned accounts, an address is derived from a public key, while smart-contract accounts are controlled by code and permissions rather than one private key. The public key can be shown to verifiers, but publishing it is not required in the same form on every chain.

Addresses can hide the underlying verification material

A public key often cannot be obtained directly from a fresh receiving address. Bitcoin address schemes may commit to a public-key hash or script, revealing different information at spending time; some spending paths involve scripts or multiple keys rather than one public key. For merchants this means a receiving address is an instruction to the sender, not the same data needed to independently verify every kind of signature. An operator who publishes an extended public key for invoice generation can avoid exposing spending keys, but it may reveal links among many customer payments. In EVM environments, smart-contract accounts can enforce multisignature or programmable authorization policies. The practical lesson is to verify recipient addresses and transaction results with the right network's rules rather than applying one key-to-address formula universally.

A real-world payment example

A customer signs an Ethereum transfer. The merchant's monitoring service can confirm that the transaction is valid under network rules without ever seeing the customer's private key. When a customer pastes an address into a checkout, however, the service should validate address formatting and network compatibility rather than treat it as a plain public key.

Limits and common misunderstandings

A public key is generally safe to share for signature verification, but address reuse and transaction linkage create privacy concerns. Never share the private key or recovery phrase. The exact security assumptions depend on the signature scheme and software implementation; a public key by itself does not give someone spending authority.

How it differs from related concepts

Private key: signs and must remain secret. Public key: verifies. Address: human-usable destination derived or assigned under network-specific rules.

Explore further

Official background: technical documentation.

Related glossary terms: Private Key, Digital Signature, Wallet Address.