Opera for desktop now includes a cryptocurrency wallet, after its Android app got one in December; wallet keys and transactions are synced between PC and mobile
Opera has updated its eponymous web browser for the desktop with a crypto-makeover and a number of additional features.
Context & Ripple Effects
Opera's wallet rollout has been methodical: a private beta on Android in mid-2018 became the first shipping browser with a built-in Ethereum wallet that December, complete with dApp and collectible support. Today's desktop update closes the loop by syncing wallet keys and transactions between PC and mobile, turning the browser itself into a cross-device crypto client rather than a per-platform add-on.
That cross-device sync is what distinguishes this step: a user's wallet follows them from phone to desktop inside one vendor's software stack, which is exactly the positioning Opera later formalized in its Crypto Browser Project and carried to iOS.
First-order effects
- Desktop Opera users can now hold and transact without installing a separate wallet or extension, and their existing Android wallet state carries over via key and transaction sync.
- Opera's browser becomes a single sign-on surface for Ethereum-based dApps on both platforms, since the same synced identity works wherever the browser runs.
Second-order effects
- Browser rivals shipping only extension-based wallets face pressure to match native integration, because Opera's synced wallet removes the install friction that has been the main cost of browser crypto use.
- Opera's rapid follow-on adding Tron's TRX and TRC-standard tokens shows the wallet is designed as a multi-chain rail, pulling token projects toward whichever browser ships their standard first.
Third-order effects
- If native wallets keep spreading across platforms, the browser displaces standalone wallet apps as the default permission layer for web3 access — the trajectory Opera made explicit with its dedicated Crypto Browser line through 2022.
- Wallet distribution consolidating into browsers would make browser vendors gatekeepers of chain and token reachability, giving them leverage over which standards users encounter by default.
The trend: Browsers are absorbing crypto wallets as built-in infrastructure, shifting web3 access from installed extensions to whatever the browser vendor ships natively.