A cryptocurrency user managing assets across Ethereum, Solana, Polygon, and a dozen other blockchains faces a practical security decision: whether to rely on a custodial exchange, which holds private keys on centralized servers, or to use a non-custodial wallet application where the user retains exclusive control. That choice involves trade-offs between convenience and custody risk. A non-custodial wallet eliminates the risk that a platform will freeze assets, suffer a breach affecting thousands of customers, or surrender keys to regulatory authorities. It transfers responsibility entirely to the individual: the user must secure their recovery phrase, update their software, and avoid phishing.

Bitget Wallet, previously known as BitKeep, operates as a non-custodial wallet available across Chrome extension, iOS, Android, Windows, and Mac. It supports over 90 blockchains, integrates with hardware wallets like Ledger and Trezor, and provides built-in access to DEX swaps, DeFi protocols, and NFT galleries. The security model is straightforward in principle: private keys are encrypted locally on the user’s device, never transmitted to Bitget’s servers, and the user alone can authorize transactions. But principle and practice diverge. Private key encryption quality, how well the application handles biometric authentication, whether local storage is actually air-gapped or inadvertently exposed, and the overall attack surface of a multi-chain, multi-feature application require careful examination.

Bitget Wallet security architecture showing private key encryption, local storage, and hardware wallet integration across multiple blockchains

Private key encryption as the foundation

The security of any non-custodial wallet begins with private key encryption. A private key is a cryptographic secret that authorizes cryptocurrency transactions. If an attacker obtains an unencrypted private key, they can move all funds associated with that key instantly and irreversibly. Bitget Wallet encrypts private keys at rest using industry-standard algorithms, meaning they are not stored in plaintext on the device. The encryption process typically uses AES-256, a symmetric cipher standardized by the National Institute of Standards and Technology and vetted across decades of cryptographic practice.

The encryption strength, however, depends on the key that encrypts the private keys themselves. That key is typically derived from the user’s password or PIN through a key derivation function such as PBKDF2 or Argon2. A weak password—one that can be guessed in millions of attempts—undermines the entire system. NIST cryptographic standards recommend that key derivation functions be computationally expensive, forcing attackers to slow down their guessing attempts. If Bitget Wallet uses a weak iteration count or insufficient salt, an attacker with access to a device could potentially crack the PIN through brute force within hours or days rather than centuries.

The practical implication is that encryption strength is not a binary property. It exists on a continuum shaped by algorithm choice, implementation details, and user behavior. A 256-bit key is theoretically unbreakable through brute force, but the user’s 4-digit PIN is not. Many mobile wallets require a PIN or biometric authentication as a convenience layer, with the assumption that device-level controls (such as biometric data, TPM, or Secure Enclave) will prevent unauthorized unlock attempts. That delegation of trust is reasonable if the device’s security is maintained, but it creates a dependency on operating system integrity.

Users considering Bitget Wallet for significant holdings should verify that their PIN is sufficiently long (at least 6–8 digits, or a passphrase if the application supports it) and that they have disabled automatic unlock features on the phone itself. A child, roommate, or thief who can unlock the device may then access the wallet. The encryption protects against theft of the device’s storage drive, but not against someone with the unlocked phone in hand.

Local data storage and the air-gap boundary

Bitget Wallet stores private keys and wallet data locally on the user’s device rather than on Bitget’s servers. That architecture is called «air-gapped» in the strict sense: the sensitive material does not pass through the internet to a third party’s database. But the term «air-gapped» can be misleading. The device itself is almost certainly internet-connected, running a general-purpose operating system (iOS, Android, Windows, or Mac), and executing thousands of other applications.

Local storage therefore protects against a specific risk: that Bitget’s infrastructure will be hacked and millions of encrypted private keys will be stolen. It does not protect against malware on the user’s device, a compromised operating system update, a backup service that synchronizes the wallet file to cloud storage, or a supply-chain attack on the wallet application itself. OWASP’s cryptographic storage guidance emphasizes that local encryption is only one layer. An attacker who gains code execution on the device—through malware, browser extension, or a vulnerability in the operating system—can intercept the decrypted private key in memory, before it is encrypted, and transmit it to a remote server.

The risk of device compromise is not hypothetical. Mobile malware can be distributed through app stores, browser extensions can be modified through supply-chain attacks or developer account takeovers, and zero-day vulnerabilities in operating systems are actively exploited. A user’s device security posture must therefore be considered as part of the Bitget Wallet security model. Installing software from untrusted sources, using the same password across multiple services, connecting to unencrypted Wi-Fi, and failing to update the operating system are behaviors that can compromise the wallet regardless of how carefully Bitget encrypts the private keys.

Bitget Wallet addresses some of these concerns through local data storage and by not requiring creation of an account with Bitget servers. The user does not need to trust that a centralized database will be protected. But they do need to trust the security of their device and their own backup procedures. If the wallet’s recovery phrase is photographed, written to a cloud note, texted to a contact, or stored in a browser password manager, the encryption is worthless.

Biometric and multi-factor authentication limitations

Modern mobile devices offer biometric authentication through fingerprints (on most Android devices and older iPhones) or Face ID (on newer iPhones). These systems are designed to be faster than PIN entry and provide a second layer of authentication: a thief would need both the phone and the user’s finger or face. Bitget Wallet supports biometric authentication as an alternative to PIN entry, which is a reasonable usability improvement.

The security improvement, however, is bounded. Biometrics are not secrets in the cryptographic sense: a fingerprint cannot be changed, and it may be reproducible from images or lifted from surfaces. More importantly, biometrics unlock the device, but they do not necessarily authenticate each transaction. A wallet that requires biometric confirmation for every transaction is more secure than one that requires it once and then allows unlimited transactions, but Bitget Wallet’s transaction confirmation process should be verified based on the amount, frequency, and user preferences.

Two-factor authentication (2FA) in the context of a non-custodial wallet is often misunderstood. If 2FA is implemented through SMS codes, email confirmations, or a code generator controlled by the user, it can provide some protection against account takeover if the service is cloud-based. But Bitget Wallet is designed to operate without a cloud account. A recovery phrase is sufficient to restore the wallet on a new device without any 2FA. That design choice prioritizes self-custody and eliminates the single point of failure at Bitget’s authentication servers, but it also means that 2FA cannot prevent a user who has lost their recovery phrase from being unable to recover it.

The relevant comparison is between a custodial exchange with account-based 2FA and a non-custodial wallet with device-based PIN or biometric protection. The former can lock an account if the password is forgotten; the latter cannot. The user must take responsibility for recovery, which means keeping a recovery phrase safe.

Hardware wallet integration and air-gapped signing

For users managing larger amounts or seeking higher security, bitget wallet supports integration with hardware wallets such as Ledger and Trezor. A hardware wallet is a separate physical device designed to store private keys in isolated silicon and sign transactions without exposing the keys to the connected computer. When Bitget Wallet is connected to a hardware wallet, the application generates transactions and displays them on the hardware device’s screen. The user confirms the transaction on the hardware device itself, and the signature is returned to Bitget Wallet for broadcast.

This architecture substantially reduces the risk that malware on the user’s computer can steal private keys. Even if the computer is fully compromised, it cannot extract the key from the hardware wallet; it can only request signatures. An attacker could potentially trick a user into confirming a fraudulent transaction on the hardware device by displaying a fake transaction on the computer screen, but that requires the user to confirm on the physical device without noticing the discrepancy. Hardware wallet manufacturers design screens and interfaces specifically to make such deceptions difficult.

The trade-off is convenience and recovery. A hardware wallet requires physical possession of a separate device, which can be lost, damaged, or stolen. A recovery phrase for the hardware wallet must be backed up separately. The transaction confirmation process is slower, since the user must physically interact with two devices. For frequent small transactions, that friction is significant. For large balances or infrequent high-value payments, the security improvement often justifies the inconvenience.

Users considering hardware wallet integration should purchase directly from the manufacturer, verify the authenticity of the device through the manufacturer’s website, and test the recovery process without putting funds at risk. A counterfeit hardware wallet or one purchased from an untrusted seller may have been modified during manufacturing or shipping.

Multi-chain support and expanded attack surface

Bitget Wallet supports over 90 blockchains, including Ethereum, Solana, Polygon, Binance Smart Chain, Cosmos, Avalanche, and many others. This breadth of support is valuable for a user managing assets across multiple networks. It eliminates the need to install dozens of separate applications and keeps all recovery information in one place. But it also creates a wider attack surface. Each blockchain has its own network protocols, address formats, transaction structures, and security assumptions. A vulnerability in how Bitget Wallet handles Solana transactions would not affect Ethereum, but it could affect Solana users.

Ethereum protocol documentation specifies that Ethereum addresses are derived from public keys using the Keccak-256 hash function and that transactions must be signed with ECDSA (Elliptic Curve Digital Signature Algorithm). Solana uses a different key derivation process and Ed25519 signatures. Polygon shares Ethereum’s cryptography but operates as a separate blockchain with distinct nonce and gas-fee mechanisms. A wallet that supports all three must implement three different signing algorithms correctly. Any error—a wrong hash function, an incorrect key derivation path, or a failure to validate transaction parameters—could result in funds being lost or stolen.

The likelihood that Bitget Wallet has no implementation errors across 90+ blockchains is low. The more realistic expectation is that vulnerabilities will be discovered over time and that the Bitget team will issue updates. Users should therefore ensure that automatic updates are enabled or regularly check for available versions. A wallet that is months out of date may be running with known security vulnerabilities that attackers can exploit.

Comparing non-custodial and custodial security models

A user deciding whether to use Bitget Wallet or a custodial exchange faces fundamentally different risk categories. A custodial exchange such as Coinbase, Kraken, or Binance holds the user’s private keys on its servers. The exchange is responsible for securing those keys against theft, and the user relies on the exchange’s security practices. If the exchange is hacked, the user’s funds may be stolen. If the exchange is shut down by regulators, the user may not have immediate access to their funds. If the user forgets their exchange password, the exchange can reset it (provided they control the associated email).

Bitget Wallet reverses those responsibilities. The user controls their private keys directly, so no exchange hack can steal them. Regulatory action cannot freeze a non-custodial wallet; it can only restrict the user’s ability to move funds on-chain or to convert them to fiat currency. If the user loses their recovery phrase, the funds are permanently inaccessible, and no support team can help recover them.

Regulatory frameworks reflect these differences. The UK’s Financial Conduct Authority has issued guidance on cryptocurrency custody and wallet providers, distinguishing between custodial services (which hold customer assets and are subject to regulatory oversight) and non-custodial applications (which do not hold assets and are therefore often considered outside the regulatory perimeter). The European Securities and Markets Authority has similarly distinguished custodial and non-custodial arrangements, with custodial services facing stricter requirements for client asset protection. That regulatory distinction reflects the different trust models: a custodian is expected to be regulated, insured, and subject to regular audits. A non-custodial wallet is not.

From a security perspective, the choice depends on the user’s threat model. A user concerned primarily about exchange hacking or regulatory freezing should use a non-custodial wallet. A user concerned primarily about personal device security or the risk of losing a recovery phrase might prefer the simplicity of an exchange, accepting the custodial risk in exchange for account recovery options and professional security management.

Practical security measures for Bitget Wallet users

A non-custodial wallet is as secure as the user makes it. The best encryption and hardware wallet integration cannot prevent a user from writing their recovery phrase on a sticky note, taking a screenshot of it, or entering it into a phishing website. Security practices matter as much as the application’s technical design.

First, create the recovery phrase in a secure environment. Write it down on paper, store it in a safe or safe-deposit box, and never type it into a computer. If the recovery phrase must be entered into the wallet again (for example, to restore it on a new device), do so only on the device where the wallet is being restored, and wipe the clipboard afterward to prevent accidental exposure.

Second, use a strong PIN and enable biometric authentication if the device supports it. The PIN should be at least 6–8 digits and not based on birthdays, anniversaries, or other guessable information. Device-level encryption and biometric authentication should also be enabled, creating multiple barriers between an attacker and the wallet.

Third, keep the wallet application and the operating system updated. Security patches are released regularly, and running outdated software is a common vector for compromise. Enable automatic updates where possible.

Fourth, if storing large amounts, consider a hardware wallet. The integration with Ledger or Trezor adds a significant security layer by isolating key storage on a separate device.

Fifth, be cautious with integrations. Bitget Wallet provides access to DEX swaps and DeFi protocols. Before approving a transaction that interacts with a smart contract, understand what permissions the contract is requesting. A contract that requests unlimited token approval can drain that token type from the wallet if the contract is malicious.

Future security considerations and evolving threats

The security landscape for non-custodial wallets is evolving. New attack vectors emerge as attackers develop better techniques for device compromise, side-channel attacks on cryptographic implementations, and social engineering. The Bitget team’s ability to respond to these threats—through regular updates, security audits, and adoption of emerging best practices—will determine whether the wallet remains secure long-term.

The US Commodity Futures Trading Commission has stated that wallet providers should maintain security standards commensurate with the assets they safeguard, though the CFTC’s regulatory authority over non-custodial wallets remains limited. Custody standards for institutional assets typically require regular third-party security audits, insurance, and compliance with SOC 2 Type II or equivalent frameworks. A non-custodial wallet such as Bitget is not subject to those requirements, but users can ask whether Bitget has undergone independent security audits and whether the results are publicly available.

The increasing sophistication of hardware wallets, the adoption of threshold cryptography (splitting a private key across multiple devices or people), and the development of post-quantum cryptographic algorithms are all areas where non-custodial wallets may evolve to offer better security. Whether Bitget Wallet will incorporate these advances is a question for users to monitor over time.

Frequently asked questions

Is Bitget Wallet truly non-custodial?

Yes. Bitget Wallet is a non-custodial application where private keys are stored locally on the user’s device, encrypted with the user’s PIN or password, and never transmitted to Bitget’s servers. The user has exclusive control over the keys and therefore exclusive control over the funds. There is no account recovery process through Bitget; only the recovery phrase can restore the wallet.

What happens if I lose my recovery phrase?

If you lose your recovery phrase and do not have it written down elsewhere, the funds are permanently inaccessible. There is no way to recover the phrase, and no support team can retrieve it. This is a core feature of non-custodial design: Bitget cannot access your keys, so it cannot recover them for you. Always store your recovery phrase securely before creating a wallet.

Does Bitget Wallet support two-factor authentication?

Bitget Wallet supports biometric authentication (fingerprint or Face ID) and PIN protection on the device level, which acts as a security layer between an attacker and the wallet. However, since the wallet is non-custodial and does not rely on cloud accounts, traditional 2FA through SMS or email is not part of the security model. Device-level security is the primary defense.

Can I use Bitget Wallet with a hardware wallet like Ledger?

Yes. Bitget Wallet integrates with hardware wallets such as Ledger and Trezor, allowing you to store private keys on a separate device and sign transactions through the hardware wallet’s secure interface. This is recommended for large holdings, as it isolates keys from your computer and protects against malware.

How does Bitget Wallet’s multi-chain support affect security?

Supporting over 90 blockchains expands the attack surface because each blockchain has different cryptographic requirements. Bitget Wallet must correctly implement different signing algorithms and transaction formats. However, this is managed through regular security audits, updates, and patches. Users should ensure they are running the latest version of Bitget Wallet and remain cautious when interacting with unfamiliar smart contracts.

Abrir chat