Opera is testing a built-in crypto wallet in its Android browser, with support for Ethereum-based tokens, collectibles, and DApps, available in private beta now
Cryptocurrencies: They're kind of a big deal. Bitcoin, one of the most popular digital currencies on the market …
Context & Ripple Effects
This July 2018 private beta was the first step in a strategy Opera executed methodically: five months later it shipped the same built-in Ethereum wallet to all Android users, collectibles like CryptoKitties included (general Android release), then brought the wallet to desktop in April 2019 with keys and transactions synced between PC and mobile (desktop rollout).
The bet compounded from there — Tron's TRX and TRC-standard tokens were added to the browser wallet within a year (Tron support), and by 2022 Opera had productized the whole idea as a dedicated Crypto Browser Project spanning Windows, Mac, and Android (Crypto Browser Project) plus an iOS build supporting Ethereum, Polygon, and Celo (iOS Crypto Browser). The Android beta matters because it is where the browser-as-wallet thesis was first tested.
First-order effects
- Android beta testers get Ethereum tokens, collectibles, and DApps inside the browser itself — no separate wallet app or extension — making Opera one of the first mainstream mobile browsers to ship native crypto access.
- Ethereum DApp developers gain a mobile distribution surface they lacked in Chrome-based browsers, since Opera's embedded wallet removes the install friction that gated mobile Web3 usage.
Second-order effects
- Competing blockchain ecosystems take note and negotiate their way in — Tron's TRX and TRC-token support landing in the same wallet a year later shows chain projects treating browser distribution as a battleground.
- Rival browser vendors face pressure to match native wallet functionality or cede the crypto-native user segment, a pressure Opera escalated by later spinning the feature into a standalone cross-platform Crypto Browser.
Third-order effects
- If the pattern holds, the browser displaces the standalone wallet app as the default permission layer for web3 — the wallet becomes a browser feature the way password managers did, with platform owners controlling which chains and DApps are reachable.
- Browsers that own the wallet layer also own the exchange and dApp entry points built on top of it, shifting gatekeeping power in crypto from wallet startups toward browser/platform incumbents.
The trend: Web browsers are absorbing the crypto wallet as a built-in permission layer, turning the browser rather than the standalone app into the primary gateway to tokens, collectibles, and DApps.