wallet-security

A <a href="https://crypto-bible.com/en/glossary/wallet-and-security/hardware-wallet/" target="_blank" rel="noopener">Hardware Wallet</a> signing raw hexadecimal data or a hash without sufficient context, unable to decode it into transaction details a human can actually understand.

The practice of keeping a <a href="https://crypto-bible.com/en/glossary/wallet-and-security/private-key/" target="_blank" rel="noopener">Private Key</a> entirely within an environment that has never touched the internet, so a hacker has no remote channel to reach it at all — it's the most effective method within self-custody against the specific threat of a hacker stealing a key over a network connection. It's a category (any offline way of keeping a private key qualifies), not a single product; a <a href="https://crypto-bible.com/en/glossary/wallet-and-security/hardware-wallet/" target="_blank" rel="noopener">Hardware Wallet</a> is just one of the most common ways to implement <a href="/en/glossary/wallet-security/cold-storage/">Cold Storage</a>.

A formal procedure in which multiple authorized personnel are present together, following a predetermined script, to generate and distribute private keys for multisig or institutional-grade crypto assets, ensuring geographic and device separation is implemented from the very start.

A wallet that requires multiple independent private keys to jointly approve any transaction — a 3-of-5 setup means at least three out of five keys must agree before a transaction goes through, so a single compromised, lost, or rogue holder can't move funds alone. But this protection only covers the signing authority itself, not whether the content each signer actually sees and verifies has been tampered with.

A sequence of 12 or 24 words that serves as the root from which all of a wallet's private keys are derived — whoever holds it holds everything in the wallet, and no password or 2FA can stand behind it.