If you keep crypto in a hardware wallet, a handful of terms will keep recurring in support threads and error messages. I wrote this glossary to put those terms in one place and tie each entry to useful troubleshooting and setup guides on the site. I believe clarity reduces mistakes (which is where most user losses come from). What follows moves from basic definitions to practical checks and links you can use right away.
BIP-39 definition: a standard that defines how a seed phrase (list of words) is created from entropy and how that phrase converts into a binary seed used to derive private keys. In plain language: BIP-39 tells wallets how to turn randomness into your seed phrase and back again.
Example: if you backup a 24-word seed phrase and store it correctly, you can recover funds on any compatible wallet that supports the same wordlist and derivation method. If you mix incompatible formats, recovery may fail — see restore & recover.
Below are concise definitions you’ll see across troubleshooting docs.
If a term shows up in an error code you don’t understand, check error-codes-index or the troubleshooting flowchart to map words to actions.
secure element glossary: a secure element is a tamper-resistant chip that stores private keys and performs cryptographic operations without exposing keys to the rest of the device. Think of it as a locked vault inside the device.
Why it matters: a secure element makes extracting private keys far harder for attackers who get physical access. That said, secure elements differ by vendor and implementation, and they are one piece of a broader security model (supply chain, firmware signing, and user practices matter too).
Want technical reading? See the architecture notes in [secure-element-architecture]. And if you’re worried about counterfeit units or supply-chain attacks, read [fake-supply-chain-security] and [where-to-buy] before you buy.
![placeholder: secure element architecture diagram]
What is a seed phrase? A seed phrase (recovery phrase) is the human-friendly backup that lets you restore private keys. A common choice is 12 or 24 words derived under the BIP-39 definition.
12 vs 24 words: 12 words are shorter and easier to copy correctly. 24 words increase entropy and make brute-force attacks significantly harder. In my testing, I still prefer 24 for long-term cold storage, but the right choice depends on your threat model.
Passphrase (25th word): an optional secret added to the seed phrase derivation (sometimes casually called the 25th word). It acts like an additional password on top of your seed phrase. Useful? Yes, for plausible deniability and extra security. Risky? Also yes: lose the passphrase and the funds are irrecoverable. See practical guidance at [passphrase-25th-word] and [passphrase-management].
For physical backups, use metal plates or stamped steel (not paper) for long-term durability. See [seed-backup-security] and [legal-backup-considerations]. And yes, I once saw a paper backup degrade beyond legibility after a decade in a drawer.
What is air-gapped? An air-gapped device never connects directly to the internet during signing. Transactions are prepared on an online machine, transferred to the air-gapped device (via QR, microSD, or USB), signed offline, then returned.
Connectivity modes — quick comparison:
| Connection | Typical use | Security notes | Troubleshooting tip |
|---|---|---|---|
| USB (cable) | Common desktop/mobile | Fast and simple; physical access required | Check OS drivers and [usb-os-connectivity] |
| Bluetooth | Mobile convenience | Adds remote attack surface if implementation is weak | Turn off Bluetooth if you prefer wired-only security; see [usb-otg-bluetooth] |
| NFC | Quick tap signing | Short-range, but still a wireless channel | Retry with clean pairing; check mobile permissions |
If you prefer fully offline signing, follow the guide on air-gapped setups in [cold-storage-strategies] and the [multisig-setups] for redundancy.
multisig glossary: multisig (multi-signature) is a spending policy that requires signatures from multiple independent devices or keys. Common setups include 2-of-3, 3-of-5, etc.
Why use multisig? It reduces single-point-of-failure risk. If one key is lost, other cosigning keys can still recover funds. It also helps with inheritance planning and geographic distribution.
Example workflow: you keep two keys in separate safe deposit boxes and one on an air-gapped device at home. A 2-of-3 policy lets you spend if one location is inaccessible.
Compatibility note: multisig requires wallet and service compatibility — check guides like [multisig-setup], [electrum-integration], and [wallet-integration-hub] before deploying.
Backup method comparison:
| Method | Strength | Recovery complexity | When to use |
|---|---|---|---|
| 12-word seed | Moderate | Simple | Daily users who trade frequently |
| 24-word seed | High | Simple but longer | Long-term cold storage |
| SLIP-39 (Shamir) | Flexible (shares) | Moderate | Distributing shares across locations |
| Metal plate backup | Durable | Simple | Long-term, fire/water resistant storage |
Connectivity risks summary:
| Channel | Risk level | Mitigation |
|---|---|---|
| USB | Low with good drivers | Use verified cables, update firmware ([firmware-updates]) |
| Bluetooth | Medium | Disable unless needed, review permissions |
| Air-gapped (QR/SD) | Low | Ensure offline host is clean |
If you’re hunting a specific error, start at [error-codes-index] and follow the [troubleshooting-flowchart].
Q: Can I recover my crypto if the device breaks?
A: Yes — if you have the seed phrase/recovery phrase or SLIP-39 shares. Follow [recover-from-seed] or [sweep-recover-software-wallets] for options.
Q: What happens if the company goes bankrupt?
A: Your funds are non-custodial if you control the seed phrase. See [lost-device-company-bankrupt] for practical steps (and the legal backup considerations in [legal-backup-considerations]).
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth adds convenience and a potential attack surface. It can be acceptable with strong device security and up-to-date firmware, but avoid it if your threat model assumes remote attackers. See [usb-otg-bluetooth] and [connectivity-security].
Glossaries remove guesswork and help you follow the right troubleshooting path fast. Start by bookmarking [troubleshooting-index] and the guides linked above. If you want a recommended path: verify your seed phrase format (BIP-39 definition), check firmware status ([firmware-updates]), and confirm whether your device is air-gapped or connected.
If you still have trouble, follow the flowchart at [troubleshooting-flowchart] and consider reaching out to community alternatives listed at [support-alternatives]. But remember: never share your seed phrase or passphrase with anyone.
Want more step-by-step help? See the setup guide ([setup-guide]) and seed management walkthrough ([seed-phrase-management]).