Zero technical specs. Zero audit trail. Zero verifiable claims. That is the entirety of Bitget Wallet’s latest press release—a CMO’s monologue promising to turn a multi-chain wallet into a ‘daily financial app’ that directly competes with Neobanks. If it isn’t formally verified, it’s just hope, and this hope is wrapped in marketing gloss with no underlying code to stress-test.
Context: The Wallet-as-Super-App Playbook Bitget Wallet (formerly BitKeep) is a non-custodial wallet backed by the Bitget exchange. It supports multiple EVM and non-EVM chains, offers a built-in DEX aggregator, and claims several million users—though exact MAU numbers remain opaque. The CMO’s statement positions the wallet as a challenger to digital banks like Revolut and N26, aiming to seamlessly integrate crypto and traditional finance into a single interface.
This is not a novel thesis. MetaMask has been slowly adding fiat on-ramps via Snaps; Trust Wallet already offers direct crypto-to-fiat conversions through its Binance partnership. What sets Bitget’s claim apart is the explicit declaration of war on the Neobank sector—a sector that has spent the last decade perfecting user experience, regulatory compliance, and trust. The gap between a crypto wallet and a Neobank is not just feature depth; it is an entire infrastructure of banking licenses, insurance, and anti-fraud systems. The CMO offered zero evidence that Bitget Wallet has crossed any of those thresholds.
Core: Dissecting the Architecture Required to Deliver the Promise To evaluate the feasibility, I must reconstruct the technical requirements from first principles. Building a daily financial app on top of a non-custodial wallet involves at least five critical layers: fiat on/off ramps, account abstraction, multi-asset custody, regulatory compliance, and a sustainable economic model. Each layer introduces non-trivial failure points.
Fiat On/Off Ramps and the Licensing Trap Without a direct connection to the banking system, a wallet cannot offer debit cards, direct deposits, or bill payments. This requires money transmitter licenses in every jurisdiction (e.g., 54 state licenses in the US, an EMI license in the UK, a PSAN registration in France). Bitget Wallet has not publicly disclosed any licensing progress. From my experience consulting for a Tier-1 bank’s custody integration in 2024, I know that obtaining even a single EMI license takes 12–18 months and requires deep background checks on all key personnel. The announcement implies this is a near-term goal, yet no timeline or jurisdiction was cited.
Account Abstraction (ERC-4337) – The Silent Assumption To make the wallet user-friendly for daily payments, Batch transactions, social recovery, and gasless meta-transactions are mandatory. The industry standard for this is ERC-4337, which is still in its experimental phase. I have audited three implementations of ERC-4337, and each contained at least one critical vulnerability—usually in the Entry Point contract’s replay protection or in the paymaster’s gas price oracle. If Bitget Wallet intends to deploy account abstraction without a formal verification of its Entry Point fork, it will introduce a systemic risk surface. The user base may hold millions in assets, and one bug in the social recovery module could enable permanent fund freezing or theft. Code is law, but law is interpretive when the code has not been formally verified.
The Hybrid Custody Model – A Security Gap To offer both crypto self-custody and fiat bank accounts, the wallet will likely maintain a hybrid model: non-custodial for crypto, and custodial for fiat accounts (held by a licensed partner). This dual-architecture expands the attack surface. The fiat side depends on the security of the partner’s backend, which is opaque to the user. The crypto side relies on the user managing their own private keys, which has historically led to high rates of loss or theft. In my 2020 review of Compound’s liquidation mechanics, I saw how composability across different security domains (smart contract + off-chain oracle + centralized keeper) could cascade into systemic failure. A hybrid wallet is inherently more complex than a pure DeFi protocol.
Economic Model – Where Does the Yield Come From? Bitget Wallet does not have a native token; it relies on the Bitget exchange’s BGB token for some utility. To compete with Neobanks that generate revenue through interchange fees, interest margins, and subscription plans, Bitget must either introduce a new token or extract fees from crypto-native activities (swap fees, withdrawal charges). The latter can produce revenue but at a scale far below that of a Neobank. Without a clear value capture model, the “daily financial app” remains a cost center, not a profitable business. I have seen similar ambitions from other wallets—Rainbow, Zapper, DeBank—all of which have pivoted to NFTs or memecoins because the super-app model proved unsustainable.
Contrarian: The Blind Spots the CMO Overlooked Behind the optimistic narrative lie three systematic blind spots. First, the regulatory environment for crypto-fiat hybrids is rapidly tightening. In 2025, the MiCA regulation in Europe imposes strict capital requirements for e-money wallets, and the US SEC’s recent assertions over broker-dealer definitions could capture any wallet that offers fiat custody. Second, the assumption that crypto users want a single app for all financial needs contradicts data: according to a 2024 DappRadar survey, 68% of active wallet users maintain at least two different wallets—one for DeFi activity and one for long-term storage. The “super app” theory has been disproven by user behavior. Third, the security burden on users for non-custodial keys remains the strongest adoption barrier. Even with account abstraction, the recovery process is unfamiliar to the average consumer. The standard is obsolete before the mint finishes—the race to build a Neobank-killer may end before the first beta test.
Takeaway: Vulnerability Forecast Bitget Wallet’s announcement is a high-level vision statement with no verifiable technical delivery. In the next six months, I will watch for two signals: publication of a formal verification of their smart account architecture, and filing of at least one money transmitter license in a major jurisdiction. If neither appears, the narrative will fade, and the only risk left is that users pour liquidity into a product that cannot deliver the promised safeguards. The market should treat this as noise until the code is open-sourced and audited by a third-party with a track record in formal verification. As I tell my students: trust the hash, not the hype—unless the hash is part of a formally verified contract.