A signing key and a wallet backup serve different purposes

A private key can create signatures for the permissions associated with that key. A recovery phrase can recreate the starting point for a whole wallet. In a wallet that combines BIP-39 and BIP-32, the BIP-39 words and any optional passphrase produce a seed. BIP-32 uses the seed to derive a hierarchy of keys. The corresponding assets remain recorded on their blockchains.

Why a restored wallet can show different addresses

The same seed and derivation path lead to the same derived key. Wallets can use different paths for accounts, address types, or networks. A second app may therefore show unfamiliar addresses even when it accepts the same recovery words. If the wallet uses a BIP-39 passphrase, a typo or a missing passphrase produces a different seed. A local PIN or app password usually unlocks the software or device and is separate from that optional passphrase.

What a leak gives someone access to

With an ordinary private key for one account, someone can act with that key’s signing authority. With the recovery words and any necessary passphrase, they may be able to reproduce keys across many accounts in the wallet. Changing the app password cannot take away a copied key’s signing authority. In a multisignature setup, the effect of losing one key depends on how many signers are required and whether that key is used elsewhere.

Keep recovery secrets out of support requests

A block explorer can show public account activity using an address alone. A support message asking for recovery words or a private key is a warning sign. Keep those secrets out of chats, screenshots, and online verification forms. When reading recovery instructions, check which backup standard and derivation scheme the wallet uses before entering sensitive information.

Sources

  1. BIP-39:助记词与种子规范
  2. BIP-32:分层确定性钱包规范
  3. Ethereum 官方安全与防诈骗指南

Prepared with AI assistance. This guide explains protocol behavior for educational use.

Editorial policy (Chinese)