The latest version of the Opera for Android, currently available in a private beta, introduces an easy-to-use and built-in cryptocurrency wallet functionality to the browser. This means that a significant part of Opera’s 322 million user base across all platforms would no longer need to install separate extensions to handle supported crypto payments on mobile devices.
Opera for Android With Crypto Wallet
The developers, which last year implemented an anti-mining security feature, explain that Opera with Crypto Wallet for Android’s user interface is designed to be simpler than most current crypto wallets. And Opera relies on the Android operating system’s secure system lock to sign transactions from the Crypto Wallet, so users don’t need to create new PIN codes or passwords to start using the wallet.
“Having a Crypto Wallet in the browser brings the cash experience to the world of online payments,” said Charles Hamel, Product Lead of Opera Crypto. “Paying with the Crypto Wallet is like sending digital cash straight from your phone, and we’ve just made it easier. This opens up new possibilities for merchants and content creators alike.”
Accelerating the Transition to Actual Payments
The beta version of the app only currently supports ETH, ERC-20 tokens and ERC-721 collectibles (which it automatically presents to the user). However, the developers plan to add support for additional cryptocurrencies in the future after just testing the waters now and seeing how the community reacts. Opera’s Crypto Wallet also comes with built-in support for the Ethereum Web3 API, which the Norwegian browser maker hopes will incentivize the creation of decentralized apps (dapps).
“We believe the web of today will be the interface to the decentralized web of tomorrow,” added Hamel.“By becoming the first major browser to open up to Web 3.0, we would like to contribute to making the internet of the future more accessible. Our hope is that this will accelerate the transition of cryptocurrencies from speculation and investment to being used for actual payments and transactions in our users’ daily lives.”
Author: Temitayo Olojede , firstname.lastname@example.org