Back to ResearchTopic: Self-Custody and Security
2026-03-2223 min read

How to Choose a Hardware Wallet: 10 Criteria to Check

C

Research Desk • Organizational attribution

Source Standard
6 source notes
Last Reviewed
2026-10-22
Not Advice
Educational research, not a recommendation to buy or sell

Choose a hardware wallet by checking it against criteria, not by brand reputation. The criteria that matter most are: firmware you or others can inspect, how the keys are protected physically, how the seed is generated, how the device talks to your phone or computer, which chains it signs for, the backup format it writes, passphrase and multisig support, a screen that shows the full address, and a way to confirm the unit is genuine.

This page covers the pre-purchase decision: each criterion, what to look for in the maker's documentation, and how six product lines describe themselves against it, checked October 22, 2026. It does not rank devices or recommend any of them. For related guides on keys, seeds and safe handling, see the self-custody and security hub.

What a Hardware Wallet Actually Protects

A hardware wallet is a small signing computer. It holds the private key, receives an unsigned transaction from software on your phone or laptop, shows you what it is about to sign, and returns a signature. The key is meant never to leave the device. For a refresher on keys and custody models, see our explainer on how crypto wallets work.

That design defends well against one threat: malware on your everyday computer reading your key. It does much less against the others:

Losing the backup. If the backup is lost and the device fails, the coins are gone.
Someone else finding the backup. A thief who has your words does not need your device at all.
Approving the wrong thing. The device signs whatever you confirm, including a token approval for a drainer contract.
A tampered unit. A device modified before delivery can generate keys an attacker already knows.
Weak key generation. A flawed random source can make a key guessable from day one, as the Coldcard case below shows.
Coercion and physical theft. Some features (passphrases, extra PINs, multisig) help here. Most do not.

Every criterion below maps to one or more of these threats. A feature that reduces none of the threats you face is a convenience, not security.

Four Questions to Answer Before Comparing Devices

Answering four questions about yourself first turns a long spec sheet into a short list of must-haves.

1. What do you hold, and on which chains? A Bitcoin-only holder can use firmware that strips out every other coin. Someone holding Ethereum tokens, Solana assets or layer 2 assets needs a device and app that sign on those chains and show the contract data on screen.

2. How often will you sign? A savings wallet touched twice a year can tolerate a slow, air-gapped workflow. A wallet used weekly will be abandoned if every signature is a chore.

3. Who else needs to reach the funds? A couple, family or small business may want shared control, which points toward multisig or split backups rather than one phrase in one drawer.

4. What is your realistic threat? For most people the largest risks are their own mistakes and phishing, not a lab attack on the chip. For someone whose holdings are publicly known, coercion and targeted tampering move up the list. The answer decides whether passphrases and multisig are worth their extra complexity.

The Hardware Wallet Criteria Checklist

Ten criteria, what to verify for each, why it matters, and the red flag that should stop a purchase. Use it with the maker's documentation open, not a review site's summary.

#CriterionWhat to verify in the maker's docsWhy it mattersRed flag
1Inspectable firmwareIs the firmware source published? Under what licence? Are builds reproducible?Lets outsiders check what the device does with your keyNo source, no audits, and no explanation of why
2Key protection hardwareSecure element or general-purpose chip? Which chip, and what certification is claimed?Resistance to physical extraction if the device is stolenVague "bank-grade chip" claims with no part named
3Connection methodUSB, Bluetooth, NFC, QR codes, microSD? Can radios be disabled?Each channel is a path for data in and outA channel you cannot switch off and will not use
4Chain and app supportWhich chains sign on-device, through which app, and with what on-screen detail?Unsupported chains force risky workarounds"Supports 1,000s of coins" with no list
5Screen and address verificationDoes the screen show the full address, amount, fee and change? Contract details?The screen is the only display your computer cannot alterTruncated addresses or blind signing by default
6Seed generationCan you add your own entropy (dice, coin flips)? Is there a published security record?A weak random source ruins every other protectionNo security advisories page at all
7Backup formatBIP-39 words, SLIP-39 shares, encrypted card or microSD backup?Decides where and how you can restoreA proprietary-only backup with no documented format
8Passphrase supportOptional BIP-39 passphrase? Character limit? Entered on device?Separates the backup from the fundsPassphrase only typed on the computer
9Multisig supportCan it act as one signer in a multisig wallet? Does it verify co-signer keys?Removes the single point of failureMultisig "supported" with no way to verify co-signers
10Supply-chain verificationSeals, numbered bags, attestation check in the app, boot-time integrity check?Detects a unit modified before deliverySold mainly through marketplaces with no authenticity check

Criterion 1: Firmware you can inspect

Firmware decides how the key is generated, what the screen shows, and what gets signed. Makers take roughly three positions:

Published source under an open licence. Anyone can read the code, and with reproducible builds anyone can confirm that the binary the maker ships matches that code. BitBox describes its firmware as fully open source and reproducible. Trezor describes its security design as open source with public code anyone can review.
Published source with restrictions. Coldcard publishes its firmware source and documents reproducible builds, but the licence pairs MIT terms with a "Commons Clause" condition that withholds the right to sell the software. Anyone can still read and rebuild it; whether the licence matters to you is a judgment call.
Mixed or proprietary. Ledger's product pages describe its operating system as proprietary, running on a secure element. Keystone publishes its firmware and hardware schematics but states that some third-party microcontroller libraries remain under vendor restrictions, and its firmware README says one library is included only as a precompiled file.

Published code is not proof of safety. Coldcard's own verification page notes that a reproducible build shows a binary matches its source, not that the source is free of bugs. What it buys is the chance for independent researchers to look.

Criterion 2: Secure element or general-purpose chip

A secure element is a chip built to resist physical attacks such as probing and fault injection. Makers often cite a Common Criteria rating such as EAL5+ or EAL6+ for it. Two cautions apply. First, the rating attaches to the chip the maker names, so it tells you nothing about the wallet's own firmware or the companion app. Second, a secure element can make inspection harder, because some chip vendors restrict what can be published about them.

Designs vary. Coldcard splits the wallet secret across two secure elements from different vendors and the main processor. BitBox requires three secrets to reach the encrypted seed: one on its microcontroller, one on its secure chip, and your device password. The useful question is not "does it have a secure element" but "what does an attacker holding my device need to defeat, and is that documented?"

Criterion 3: How the device connects

The unsigned transaction has to go in and the signature has to come out by USB, Bluetooth, NFC, QR codes, or microSD card.

"Air-gapped" usually means QR or microSD only, with no data cable or radio. For Bitcoin, this works through the Partially Signed Bitcoin Transaction format (PSBT, defined in BIP-174), which packages everything a signer needs into a file. Air gaps reduce the number of live channels, but data still crosses between devices, so the device still has to parse untrusted input safely. They also add friction, which matters if you sign often.

Bluetooth and NFC trade some attack surface for mobile convenience. Choose the channels you will use and check whether the others can be disabled. Several makers sell wired and wireless versions of the same family, so this is often a choice within a brand.

Criterion 4: Chains, apps and what the device can show

"Supports thousands of coins" usually counts chains reached through the maker's app plus third-party wallets. Three checks matter more than the headline count:

1.Is your chain supported for signing on the device itself, or only displayed in an app?
2.Does the device decode and show the transaction in readable form for that chain, or will it ask you to approve an opaque hash?
3.Will you be relying on third-party software, and is it maintained?

Bitcoin-only firmware trades the other way: less code to audit, at the cost of a second device or a firmware change if you later hold other assets. Trezor, BitBox and Keystone each offer a Bitcoin-only build or edition, and Coldcard is Bitcoin-only throughout.

Criterion 5: A screen that lets you verify what you sign

The device screen is the one display a compromised computer cannot change. Does it show the full receiving address, not just the first and last few characters? Does it show amount, fee and change separately? And on smart-contract chains, does it show what a contract call does, or does it fall back to "blind signing"?

Knowing what a valid address looks like makes on-screen checks faster; our guide to Bitcoin address types and prefixes shows each format. On Ethereum-style chains the costlier mistake is often an approval that lets a contract move your tokens later, covered in our token approval revocation guide.

Criterion 6: Seed generation and a public security record

A seed is only as strong as the randomness behind it, and some devices let you mix in your own entropy from dice or coin flips. The July 2026 Coldcard incident shows why this belongs on a buyer's checklist. According to Coinkite's security status page, a firmware bug weakened seed generation, and attackers regenerated the corresponding private keys offline and stole funds. The devices were not remotely accessed. Fixed releases followed, and the page states that updating corrects future seed generation but does not repair a seed created on affected firmware; those funds must move to a new seed. Current Coldcard firmware now requires at least 65 key presses, 50 physical die rolls, or 128 coin flips, mixed with device entropy, for each new seed.

Two lessons apply to any maker: read its security advisories and disclosure history before buying, and install current firmware before generating the seed you will use. Take advisories and migration steps only from the maker's own website, never from a social media post or an emailed link, because fake "security migration" notices are an obvious lure.

Criterion 7: Backup format and where it can be restored

The format decides whether you can recover on a different maker's device years from now.

BIP-39 recovery phrase. The common standard. It encodes 128 to 256 bits of entropy as 12 to 24 words from a fixed list of 2,048 words. Most wallets can restore it, which makes it the most portable option.
SLIP-39 (Shamir) shares. Splits the secret into several shares of 20 or 33 words, any threshold number of which restores the wallet, while fewer than the threshold reveal nothing about it. Trezor calls this Multi-share Backup and has made it the default on its Safe devices since June 2024. The SLIP-39 specification states that, for the most part, it is not compatible with BIP-39, so check that any device you might restore onto supports SLIP-39 specifically.
Encrypted digital backups. BitBox writes a backup to a microSD card and lets you optionally display the 24 words. Foundation's Passport Prime uses encrypted NFC "Keycards." These avoid handwriting errors but tie restoration to the maker's tools unless a word backup also exists.
Split-phrase schemes. Coldcard's Seed XOR splits a phrase into parts that each look like a valid phrase. Restoring needs a device or tool that implements the same scheme.

Record which format you used, and test a restore before funding the wallet. Our recovery seed checklist walks through storage, testing and the mistakes that most often lose funds.

Criterion 8: Passphrase support

A BIP-39 passphrase (often called the "25th word") is mixed with the recovery phrase to derive a completely separate wallet. Under the BIP-39 specification every passphrase produces a valid wallet, so there is no "wrong passphrase" error, only a different, usually empty, wallet.

That is both the benefit and the hazard. Someone with your words alone sees only the wallet without the passphrase, but one wrong character in your own record makes the funds unreachable. Trezor's documentation states that passphrases cannot be changed, removed or recovered. Limits also differ: Ledger allows up to 100 characters, case-sensitive; Trezor allows up to 128 characters on its current models and 50 on the older Model One. Prefer devices that let you enter the passphrase on the device rather than on your computer, and store the passphrase separately from the phrase.

Criterion 9: Multisig support

Multisig wallets require several keys, for example two of three, to move funds. With each key on its own device, ideally from different makers, one lost device, stolen backup or firmware flaw is not enough to lose the coins.

"Multisig support" should mean more than the ability to sign. The device should let you register the multisig wallet and check the co-signers' public keys, so that malware cannot quietly substitute an attacker's key when generating receive addresses. BitBox's security documentation describes multisig account registration with co-signer key verification. Coldcard documents multisig policies and a co-signing feature. Multisig adds setup and recovery complexity, so if you choose it, document the wallet configuration (sometimes called the descriptor) as carefully as the keys.

Criterion 10: Supply-chain verification

You want a way to know the unit you received is the one the maker built. Maker options include tamper-evident seals or bags with serial numbers, a cryptographic attestation check run by the companion app, and a boot-time firmware integrity check. Buying direct from the maker or an authorised reseller reduces the risk; marketplace listings increase it.

Before buying, the question is only whether such a check exists. The post-delivery steps (inspecting packaging, running attestation, confirming the device generates a fresh seed) are covered in our guide on checking a hardware wallet is genuine.

A separate decision: maker-run recovery services

Some makers offer optional services that keep an encrypted backup outside your home. Ledger's comparison page lists Ledger Recover as optional, and Foundation describes encrypted "Magic Backups" in its Envoy app. Such services lower the risk of losing a paper backup but raise questions about how you prove who you are, whether the provider keeps operating, and who could be compelled to cooperate. Treat this as a separate choice about trusted third parties, and read the service's terms before enrolling.

How Six Product Lines Describe Themselves Against the Criteria

The tables record what each maker's documentation said on October 22, 2026. They are not test results or a ranking. "Not verified" means we could not confirm the point from maker documentation, not that the feature is absent. Firmware changes often, so confirm each cell on the maker's current page.

Table 1: Firmware, hardware, connections and chains

CriterionTrezor Safe 3 / 5 / 7Ledger Nano S Plus, Nano X, Nano Gen5, Flex, StaxColdcard Mk5 / QBitBox02 / BitBox02 NovaFoundation Passport PrimeKeystone 3 Pro
Firmware sourceDescribed as open source, public codeMaker describes its OS as proprietarySource published; MIT licence plus Commons Clause; reproducible builds documentedDescribed as fully open source; reproducible buildsDescribed as open source hardware and softwareFirmware and hardware schematics published; some third-party MCU libraries vendor-restricted
Key protectionCertified EAL6+ secure element; Safe 7 lists a dual secure element designCertified secure element, CC EAL5+ or EAL6+ depending on model; Flex lists the ST33K1M5Two secure elements from different vendorsMicrocontroller plus secure chip; Nova lists a certified EAL6+ chipSecurity processor plus secure element; active tamper protectionThree secure element chips
ConnectionsUSB-C on all; Bluetooth on Safe 7USB on all; Bluetooth on Nano X and touchscreen models; NFC on Nano Gen5, Flex and StaxMicroSD, NFC, USB-C, Virtual Disk; Q adds a QR scanner and dual microSD slotsUSB-C; Nova adds Bluetooth for iPhone and iPadQR camera, Bluetooth, NFC, USB-CAir-gapped mode with QR codes; USB-C; microSD slot
ChainsThousands of coins and tokens listed; Bitcoin-only edition (Safe 3 and Safe 5 pages)500+ coins in the Ledger Wallet app; more via third-party walletsBitcoin onlyMulti edition (Bitcoin, Ethereum and ERC-20 tokens, Litecoin, Cardano and others) and Bitcoin-only editionBitcoin wallet app documented; other chains not verifiedMulti-coin firmware and Bitcoin-only firmware

Table 2: Screen, backups, passphrase, multisig and authenticity

CriterionTrezor Safe 3 / 5 / 7Ledger rangeColdcard Mk5 / QBitBox02 / NovaPassport PrimeKeystone 3 Pro
ScreenSafe 3: 0.96 in. mono, two buttons; Safe 5: 1.54 in. colour touch; Safe 7: 2.5 in. colour touchNano S Plus and Nano X: 1.1 in. OLED; Nano Gen5 and Flex: 2.8 in. E Ink touch; Stax: 3.7 in. E Ink touchMk5: screen with numeric keypad; Q: larger screen with full keyboard128 x 64 OLED (BitBox02); glass OLED (Nova)3.5 in. touchscreen4 in. touchscreen, 480 x 800
Backup formats12-, 20- and 24-word backups; Multi-share Backup (SLIP-39)24-word recovery phrase; optional Ledger Recover service24-word BIP-39 seed; Seed XOR; encrypted backupsmicroSD backup; optional display of 24 recovery wordsEncrypted NFC Keycards; SeedQR import and exportSeed phrase (recording sheets included); SLIP-39 user option not verified
PassphraseYes, up to 128 charactersYes, up to 100 charactersYes, BIP-39 passphraseNot verifiedYes (listed)Not verified
Multisig (consumer device)Not verifiedNot verified (Ledger Multisig is a separate enterprise product)Yes, multisig policies and co-signingYes, with co-signer key verificationYes (listed)Yes, PSBT multisig (listed for Bitcoin-only firmware)
Authenticity checksPackaging and device security sealsNot verifiedNumbered tamper-evident bag; GENUINE/CAUTION boot lightAttestation key checked by the app; tamper-evident bags"Security Check" supply-chain integrity featureDevice verification page exists; method not verified

Read against the checklist, two points stand out. The cells that matter most (multisig verification, authenticity checks) are the hardest to confirm from product pages, so read support documentation rather than marketing. And four of the six lines offer a Bitcoin-only option, so that question can often be settled within a brand.

A Decision Framework by Holder Profile

Match your answers from the four questions to a profile to see which checklist rows are hard requirements.

Holder profileTreat as must-haveCan relaxWatch out for
Bitcoin-only long-term saver, signs a few times a yearInspectable firmware, own-entropy option, passphrase on device, PSBT supportMobile connectivity, chain countLosing the passphrase or the multisig configuration
Multi-chain holder using DeFiClear on-screen decoding of contract calls, maintained app support for each chain, large screenAir-gap purityBlind signing and stale token approvals
Mobile-first, small amounts, frequent useReadable screen, reliable app, authenticity checkMultisigBluetooth or NFC left on when unused
Household or small business sharing controlMultisig with co-signer verification, or SLIP-39 sharesSingle-device convenienceDocumenting who holds which key or share
Publicly known holderMultisig across makers, passphrase, supply-chain checksSpeedKeeping all keys or shares in one location

Profiles overlap. A frequently used wallet with a small balance plus a rarely touched savings setup is often simpler than one device for both.

Worked Example: Turning the Checklist Into a Shortlist

A hypothetical example with stated inputs and unnamed devices, to show the method rather than point at any product.

Inputs. A holder keeps mostly bitcoin plus some ether. They sign about twice a month, mostly from a laptop. A partner should be able to reach the funds if something happens. They are not publicly known, and their main worries are phishing and losing a paper backup.

Step 1: Set must-haves from the profile. Bitcoin and Ethereum signing on the device; full-address display; passphrase entered on device; a documented backup format they can restore elsewhere; an authenticity check they can run at home.

Step 2: Set tie-breakers. Inspectable firmware with reproducible builds; ability to act as one signer in a future multisig; wired connection available.

Step 3: Filter three hypothetical candidates.

CheckDevice ADevice BDevice C
Signs BTC and ETH on deviceYesBitcoin-only firmwareYes
Full address on screenYesYesTruncated on small screen
Passphrase on deviceYesYesYes
Restorable backup format documentedBIP-39BIP-39Proprietary card only
Home authenticity checkApp attestationSealed bagNot documented
ResultPasses must-havesFails chain requirementFails three must-haves

Step 4: Read the result. Only Device A passes, so the tie-breakers are not needed. Device B is not worse; it fits a different profile.

Step 5: Plan the partner's access before buying. A 2-of-3 multisig, or SLIP-39 shares kept in separate places, would remove the single paper backup as a point of failure. That moves "multisig with co-signer verification" close to a must-have, and the shortlist is rechecked.

The method is the point: set requirements from your situation, then let the documentation eliminate candidates.

Common Mistakes and Edge Cases

Buying from a marketplace listing. Discounted units from unknown sellers are a common route to a tampered device. Buy direct or from a reseller the maker lists.
Accepting a pre-filled recovery phrase. A device that arrives with words already written down, or a card asking you to "restore" a supplied phrase, should be treated as compromised.
Assuming a firmware update repairs an old seed. As the Coldcard advisory states, updating corrects future seed generation only. If a maker reports a seed-generation flaw, the fix for existing funds is a new seed and a transfer.
Assuming Shamir shares restore anywhere. SLIP-39 shares need a wallet that implements SLIP-39. A BIP-39-only device will not read them.
Choosing Bitcoin-only firmware, then buying other assets. Plan for the assets you expect to hold, not only the ones you hold today.
Skipping the test restore. Restore from the backup before sending meaningful funds, while a transcription error can still be fixed.
Moving everything at once. When shifting funds from an exchange, send a small test transaction first and verify the receive address on the device screen. Our walkthrough on withdrawing from an exchange to self-custody covers the full sequence.

Planning for Heirs

Someone you trust should be able to learn that the wallet exists, where the backup is kept, and how the setup works, without the recovery words appearing in a will or any document that passes through many hands. Multisig and SLIP-39 shares can spread access across people or places, but they add instructions an heir must be able to follow. Write those down when you set up the device, and review them whenever the setup changes.

Your Next Step

Once you have a shortlist, the next risk point is the first hour with the device. Before you generate a seed or move any coins, read our guide to confirming a new hardware wallet is authentic, which covers packaging, attestation and first-boot checks that take minutes and help rule out a tampered unit.

Frequently Asked Questions

What matters most when choosing a hardware wallet?

Start with the criteria that guard against the most likely failures: a backup format you can actually restore, a screen that shows the full address and transaction details, and a way to confirm the device is genuine. After that, weigh inspectable firmware, passphrase and multisig support against your own threat model. Brand and chain count matter less than whether the device handles your specific assets clearly on its own screen.

Is an open-source hardware wallet safer than a closed-source one?

Published firmware lets independent researchers inspect how keys are generated and transactions are signed, and reproducible builds let them confirm the shipped binary matches the code. That makes problems more likely to be found and verified. It does not make the code bug-free, and a closed design leaves you relying more on the maker's own disclosures and any outside evaluations it commissions. Openness is best treated as one criterion with real weight, not as a guarantee.

Do I need a secure element?

A secure element raises the cost of extracting a key from a stolen device, which matters most if physical theft is a realistic risk for you. It does nothing against a stolen recovery phrase or an approval you signed by mistake. Most current devices from the makers we checked use one or more secure chips, so the more useful question is how the design is documented and what an attacker with the device would still need.

Are air-gapped wallets more secure than USB or Bluetooth wallets?

Air-gapped devices limit data transfer to QR codes or memory cards, which removes always-on connections. Data still crosses between devices, so the device must still parse untrusted input safely. The trade-off is speed: if the workflow is slow enough that you stop using the wallet, the security gain is lost.

What is the difference between BIP-39 and SLIP-39 backups?

BIP-39 encodes the wallet secret as 12 to 24 words from a 2,048-word list, and it is supported by most wallets. SLIP-39 splits the secret into several 20- or 33-word shares, any threshold number of which restores the wallet. The SLIP-39 specification states the two are mostly not compatible, so restoring SLIP-39 shares requires a wallet that implements SLIP-39.

Should I use a passphrase with my hardware wallet?

A passphrase means someone holding only your recovery words cannot reach the funds behind it, which helps if the backup is found or stolen. The cost is that a forgotten or mistyped passphrase makes those funds unreachable, since every passphrase produces a valid but different wallet. It suits people who can store the passphrase separately and reliably, and who test a restore with it before funding.

Sources

BIP-39: Mnemonic code for generating deterministic keys: word counts, wordlist and passphrase. Checked October 22, 2026.
SLIP-0039: Shamir's Secret-Sharing for Mnemonic Codes: Shamir shares and BIP-39 compatibility. Checked October 22, 2026.
BIP-174: Partially Signed Bitcoin Transaction Format: PSBT format. Checked October 22, 2026.
Trezor: Compare hardware wallets: Safe 3, 5 and 7 specifications. Checked October 22, 2026.
Trezor: What is Shamir backup?: share lengths, default since June 2024. Checked October 22, 2026.
Trezor: What is a passphrase?: passphrase limits. Checked October 22, 2026.
Ledger: Hardware wallet comparison: models, screens, connectivity, Ledger Recover. Checked October 22, 2026.
Ledger: Passphrase feature: 100-character passphrase. Checked October 22, 2026.
Coldcard: Security status: July 2026 seed-generation incident. Checked October 22, 2026.
Coldcard: Security and verification: source, builds, boot check, bags. Checked October 22, 2026.
Coldcard firmware licence (COPYING-CC): Commons Clause licence. Checked October 22, 2026.
BitBox02 product page (Wayback snapshot of September 20, 2026): editions, chips, backups. Checked October 22, 2026.
BitBox02 security features (Wayback snapshot): attestation, multisig registration. Checked October 22, 2026.
Foundation: Passport Prime: Passport Prime features. Checked October 22, 2026.
Keystone: Keystone 3 Pro and Keystone open source page: screen, chips, openness limits. Checked October 22, 2026.
Keystone 3 firmware repository: named secure element chips. Checked October 22, 2026.

CryptosEyes publishes general educational research, not investment, legal, or tax advice. Product features described here come from each maker's own documentation as checked on October 22, 2026, can change with any firmware or hardware revision, and are not endorsements. Confirm current specifications with the maker before buying, and never share your recovery phrase with anyone.

Source & Review Basis

This article is reviewed against the source types below. Source links are provided to help readers verify primary documents, market context, and methodology independently.

Reviewed against source notes and calculations
Security
Research note: This article is educational market research, not financial advice. Crypto and public equity data can change quickly; see our methodology and editorial policy for sourcing, review, and correction standards.
Important: Educational Purposes OnlyThe data, charts, treasury tracking metrics (including mNAV and SPS), and research provided on CryptosEyes.com are for informational and educational purposes only. They do not constitute certified financial, investment, or trading advice. Digital assets like Bitcoin and Ethereum are highly volatile. Always conduct your own research and consult with a registered financial advisor before making investment decisions.