Mnemonic Backup

Overview

Mnemonic schemes encode entropy and a checksum into words that are easier to copy than raw binary key material. In many wallets, the words are processed with an optional passphrase to derive seed material, which then feeds hierarchical key derivation.

Words alone do not identify the wallet, network, derivation path, script type, account indexes, or optional passphrase. A correctly copied mnemonic can therefore restore an empty-looking or different wallet in incompatible software. Anyone who obtains the complete secret may also recreate the wallet.

Users should record the exact order, verify spelling, protect the words from cameras and cloud storage, and document necessary non-secret recovery context. Passphrases require separate reliable backup. Restoration tests should occur securely. No legitimate support process should ask a user to reveal a mnemonic through chat, email, or a website.

Mnemonic Backup is not interchangeable with the wallet application or the assets controlled through it. For example, restoring a seed can reproduce keys but still fail to recover funds when network, derivation path, script type, account index, passphrase, or contract configuration is missing.

For Mnemonic Backup, risks include weak generation, exposed backups, phishing, malware, unauthorized export, compromised devices, incorrect derivation metadata, unavailable recovery shares, and silent policy bypass. For Mnemonic Backup, encryption at rest is useful but does not replace access control, separation of duties, tamper evidence, and tested recovery.

Audit records should link Mnemonic Backup to its key or share identifier, algorithm, derivation or policy metadata, requester, approver, device or service, payload digest, signature result, time, environment, and resulting transaction. For Mnemonic Backup, secret material itself should never be copied into ordinary logs or support records.