SEED·KNOT

Comparison

Wallet type comparison

Most comparison tables only list what each option protects you from. The load-bearing section here is number three — what it cannot protect you from. A false sense of security is worse than none.

Illustration: who holds it, blocks, cannot block and amount arranged on a seed-card grid

01Who holds the key

This is the root difference between the four; everything else follows from it. The test is simple: did setup make you write down a seed phrase.

Key custody and recovery
TypeWho holds the keyIf you forgetID required
Exchange accountThe platformRecovery flow, usually worksYes
Mobile walletYou, in local phone storageThe seed phrase, with no alternativeNo
Browser extensionYou, in extension storageThe seed phrase, with no alternativeNo
Hardware walletYou, in an offline deviceThe seed phrase, with no alternativeNo

There is also the category of exchange-branded Web3 wallets, which take one of the shapes above but vary in recovery design — some are ordinary self-custody, others split recovery across parties including the platform. Read the documentation on recovery rather than the brand.

02What each blocks

Coverage
TypeMain risks it blocks
Exchange accountYou losing the credential, you making an irreversible mistake, and being phished but still having an appeals channel; risk systems intercept some anomalous withdrawals
Mobile walletPlatform failure and platform-imposed freezes; biometrics stop someone who picks up the phone
Browser extensionPlatform risk; lets you interact with sites on a computer without handing them a key
Hardware walletPlatform risk; a program on a networked device reading the key; an independent screen for verifying what you are signing

03What each cannot block (this is the column that matters)

None of them stops you pressing confirm on a cloned page. Hardware included — it locks the key away, and the judgement stays with you.

Cannot block
TypeCannot block
Exchange accountThe platform itself failing; regulatory or risk-based freezes; funds received peer-to-peer being caught up in an upstream case; your password and verification methods being compromised
Mobile walletSeed phrase exposure; malicious approvals; counterfeit apps; clipboard address swaps; sending to the wrong address; losing your own backup
Browser extensionAll of the above, plus counterfeit extensions, malicious page scripts prompting signatures, and everything else running on that computer
Hardware walletSeed phrase exposure or loss; a phishing site persuading you to press confirm on the device; malicious approvals; sending to the wrong address; a device of unknown provenance that was tampered with
How to read this table properly

Three of the four have nearly identical cannot-block lists, and all three begin with seed phrase exposure and malicious approvals. Which tells you something: buying a more expensive wallet does not address the main risks. What does is getting seed phrase storage right (self-check) and learning to read signature prompts (how).

04Amounts and everyday friction

Fit and experience
TypeSuitsFrictionTypical use
Exchange accountWhatever you actively tradeLowFiat in and out, buying and selling, temporary parking
Mobile walletWhat you could lose today without it matteringLowEveryday sending, QR codes, small on-chain operations
Browser extensionSame; pocket money onlyMediumInteracting with applications on a computer
Hardware walletClearly more than the device costs, held long termHigh; the device comes out each timeLong-term storage

No row here is "the best one". Friction and security scale together, and an arrangement too tedious to maintain will not be maintained — a hardware wallet you find annoying enough to skip backing up is more dangerous than a phone wallet you back up properly.

05Combining them

Most people should not pick one. Split into three by purpose: an exchange for what you trade, an everyday wallet for pocket money, and a vault wallet for the bulk that connects to nothing.

Three-column diagram: exchange account, everyday wallet and vault wallet with what each holds and the risk each carries
The value here is not that any layer is especially safe. It is that a problem in one layer does not reach the others.
  1. Exchange account: fiat and trading. Configure two-factor, a withdrawal whitelist and an anti-phishing code.
  2. Everyday wallet (mobile or extension): connecting to sites and joining activity. Small amounts only, so a bad outcome has a ceiling.
  3. Vault wallet (hardware, or a hot wallet that never connects): receives, and sends only to your own addresses.

Related judgements are in hot wallets and cold wallets and Web3 wallet vs exchange account.

And one more option

If this table makes a three-layer structure sound like too much and you have no plans to do anything on-chain, using only the first layer is a perfectly coherent choice. Who does not need a Web3 wallet is about exactly that.

06Common questions

Which type of wallet is safest

There is no absolute answer. Hardware is strongest on keeping the key away from networked devices, but like every other type it cannot stop seed phrase exposure, malicious approvals or sending to the wrong address. Safety depends more on habits than on the category.

Does an exchange's own wallet count as a Web3 wallet

It depends on the product. If setup makes you write down a seed phrase and states clearly that it cannot be recovered, that is self-custody. If a phone number or email can restore access, recovery is not entirely in your hands. Read the documentation, not the brand.

Extension or mobile wallet — which is better

They serve different purposes. Extensions suit interacting with sites on a computer; mobile suits carrying around and scanning codes. Extensions add the browser environment and counterfeit listings to the risk surface, and both should hold only small amounts.

Do I need more than one wallet

At minimum, separate the one you connect to sites from the one holding your assets. That caps the damage from a mistaken approval at whatever is in the small wallet. Whether to add a hardware layer depends on the amount.