On 8th August, MetaMask, an Ethereum-based browser extension announced on Twitter that they will stop automatically injecting an Ethereum Provider or a Web3 instance at page load time on browsers. The decision was made to enhance privacy for users throughout the centralized web and will take effect on 2nd November.
MetaMask’s official announcement | Source: Twitter
An Ethereum provider links users to a running node [a procedure where nodes harmonize themselves to the network by downloading blocks that are new to them.]. A node has the capability to view and interact with the blockchain.
A Web3 instance is a compilation of modules which consist of specific functionality for the Ethereum network.
According to this upcoming change, decentralized applications [dApps] will now have to ask the Ethereum provider to get access from the browser. The browser will, in turn, request the user to accept or reject entry to the Ethereum blockchain. Once the user grants access, the Ethereum provider will be injected into the webpage and the decentralized application will start operating customarily.
MetaMask is a browser extension which was founded in 2016. Its goal is to help the users access the decentralized web in a much easier manner. Earlier, dApps were able to suggest transactions and examine the account addresses of the users.
MetaMask in their blog stated that their decision to stop injecting Web3 is to maintain the privacy of users. Other decentralized browsers such as Status, Mist, and imToken who have admitted to being mindful of confidentiality have also decided to implement the modification.
Also, MetaMask affirmed that the move will affect not just end-users but developers as well. They further stated that MetaMask keeps away from breaking interactions between an enterprise and an API [Application Program Interface], in order to guard the durability of existing sites. The platform’s concern for Ethereum users and the evident privacy flaws that subsist because of Web3, has led them to make these breaking changes.
A Twitter user named _Spdz commented:
“Super excited for this change. can’t wait to implement it.”
A Twitterati named Nicksalloum_ says:
“Good move! I especially like the removing of injection of a web3 instance. It should be up to the dApp to do what they want with the Ethereum provider, and to use `new Web3(new Provider)` if they want web3 convenience.”
Steve_flash, another Twitter user remarked:
“I never knew there were so many privacy issues, especially with fingerprinting. Ty for highlighting this and improving.”
The post MetaMask to stop injecting Web3 soon, positive news for developers and end-users appeared first on AMBCrypto.
Source: AMBcrypto
Original Post: MetaMask to stop injecting Web3 soon, positive news for developers and end-users
