How Does a Crypto Wallet Generate a New Address? (The Process Explained)

Public Key Cryptography Foundation

1. A crypto wallet begins address generation by creating a cryptographically secure random seed phrase, typically 12 or 24 English words.

2. This seed serves as the root for deterministic key derivation using standards like BIP-32 and BIP-44.

3. From the seed, the wallet derives a master private key through hashing algorithms such as HMAC-SHA512.

4. The master private key then generates hierarchical child private keys via elliptic curve multiplication on secp256k1.

5. Each child private key corresponds uniquely to a child public key using point multiplication on the same curve.

Address Encoding and Format Conversion

1. The wallet applies SHA-256 to the compressed public key to produce a 256-bit hash.

2. That hash undergoes RIPEMD-160, yielding a 160-bit result known as the public key hash.

3. A network-specific version byte is prepended—0x00 for Bitcoin mainnet, 0x6f for testnet.

4. A double SHA-256 checksum is computed from the extended hash and the first four bytes are appended.

5. The resulting byte string is encoded in Base58Check, eliminating ambiguous characters like 0, O, I, and l.

Derivation Paths and Account Isolation

1. Wallets follow BIP-44 paths such as m/44'/0'/0'/0/0 to isolate coin types, accounts, and change chains.

2. Each path component modifies the derivation index and hardened flag, producing distinct private keys even from identical seeds.

3. External chains (index 0) generate receiving addresses, while internal chains (index 1) produce change addresses.

4. Reusing the same path yields identical addresses; incrementing the final index creates a new, non-repeating address.

5. Hardware wallets perform all derivations internally, never exposing private keys to host devices during address creation.

Onchain Address Validation Mechanisms

1. Nodes verify address validity by decoding Base58Check and confirming checksum integrity before transaction relay.

2. ScriptPubKey construction differs per address type: P2PKH uses OP_DUP OP_HASH160 [hash] OP_EQUALVERIFY OP_CHECKSIG.

3. SegWit addresses (bech32) involve different hashing steps—SHA-256 followed by witness program encoding with human-readable parts.

4. Taproot addresses require Merkle root commitments and Schnorr public key serialization before bech32m encoding.

5. Invalid checksums or malformed script templates cause immediate rejection by full nodes during mempool validation.

Frequently Asked Questions

Q: Does generating a new address require internet connectivity?No. All cryptographic operations occur locally. Internet access is only needed to broadcast transactions or query balances.

Q: Can two different wallets produce the same address from different seeds?The probability is negligible—approximately 1 in 2¹⁶⁰ for P2PKH due to RIPEMD-160’s collision resistance properties.

Q: Why do some wallets show multiple addresses simultaneously?They pre-generate a lookahead window of unused addresses to support gap limits, ensuring deterministic recovery without scanning every blockchain block.

Q: Is it safe to share a receiving address publicly?Yes. Public addresses reveal no private key information. However, linking multiple addresses to one identity may compromise privacy through chain analysis.