What Is a Public Key and Private Key in Blockchain?

Public Key Fundamentals

1. A public key is a cryptographic value derived from a private key using elliptic curve multiplication.

2. It serves as the foundation for generating blockchain addresses used to receive digital assets.

3. Public keys are mathematically irreversible — no algorithm can reconstruct the original private key from it.

4. In Bitcoin, the public key is hashed twice (SHA-256 followed by RIPEMD-160) to produce a P2PKH address.

5. Ethereum uses a different derivation path: the Keccak-256 hash of the uncompressed public key yields the final address.

Private Key Mechanics

1. A private key is a 256-bit random integer selected from a finite field defined by the secp256k1 elliptic curve.

2. Its secrecy is absolute — exposure grants full control over associated funds and smart contract permissions.

3. Wallet software generates private keys via cryptographically secure pseudorandom number generators (CSPRNGs).

4. Hardware wallets isolate private key generation and signing operations within secure enclaves.

5. Loss of a private key means permanent, irreversible loss of access to all assets tied to its corresponding address.

Address Generation Process

1. Addresses are not stored on-chain but computed deterministically from public keys through standardized hashing.

2. Bitcoin supports multiple address formats: legacy (P2PKH), segwit (P2WPKH), and taproot (P2TR).

3. Ethereum addresses omit checksum validation by default, though EIP-55 introduces mixed-case checksums.

4. Solana uses base58 encoding of the SHA-256 hash of the public key to generate 32-byte addresses.

5. No blockchain stores private keys — they exist exclusively off-chain and must never be transmitted over networks.

Hierarchical Deterministic Wallets

1. HD wallets use BIP-32 to derive child keys from a master seed without exposing the root private key.

2. BIP-39 defines mnemonic phrases — 12 or 24 English words encoding a 128- or 256-bit seed value.

3. BIP-44 specifies a five-level path structure (m / purpose' / coin_type' / account' / change / address_index) for organizing accounts.

4. Each derivation step applies HMAC-SHA512 to ensure deterministic yet unpredictable key chains.

5. A single mnemonic phrase can regenerate all private keys across multiple cryptocurrencies and accounts.

Cryptographic Assurance in Practice

1. ECDSA signatures bind transactions to private keys while remaining verifiable via public keys alone.

2. Signature malleability was addressed in Bitcoin with Segregated Witness, separating signature data from transaction inputs.

3. Schnorr signatures — adopted in Bitcoin’s Taproot upgrade — enable signature aggregation and improved privacy.

4. EdDSA replaces ECDSA in Cardano and Solana, offering faster verification and resistance to side-channel attacks.

5. Every confirmed transaction on a blockchain cryptographically proves ownership without revealing the private key.

Frequently Asked Questions

Q: Can two different private keys generate the same public key?A: No. The elliptic curve discrete logarithm problem ensures a one-to-one mapping between private keys and public keys within the same curve parameters.

Q: Is it safe to share a public key before deriving an address?A: Yes. Public keys themselves pose no security risk, though exposing them early may reduce privacy in certain protocols like Bitcoin’s P2PK.

Q: Why do some wallets display both compressed and uncompressed public keys?A: Compressed keys halve storage requirements by encoding only the x-coordinate plus parity information; older systems may require uncompressed versions for compatibility.

Q: Does changing a wallet’s password affect the private key?A: No. Passwords only encrypt local wallet files; the underlying private key remains unchanged unless explicitly regenerated.