The July 25 removal of MetaMask—a browser-based Ethereum wallet—from the Google (NASDAQ:GOOGL) Chrome Web Store sparked a panic inside of the community. MetaMask itself attempted to fight the removal but received no answer only to find out later that the emails weren’t sending, as we can read in the team’s statement.
Only six hours after its removal, the extension was reinstated with Google claiming that the incident occurred because of an error.
“No email from Google at the time alerted us as to why it was taken down, though later, we were informed that the email supposedly bounced,” wrote Kevin Serrano, a team member.
During the fiasco yesterday, Charles Hoskinson—CEO of IOHK, the company developing Cardano—asked MetaMask’s Twitter account to PM him, receiving a reply that pointed him to the team’s support email address. His reaction to this wasn’t the friendliest.
https://twitter.com/IOHK_Charles/status/1022368499019210752
“We’ll be sure to return the favor if they ever have any questions about Daedalus, Zencash, Ethereum Classic, Cardano, or the other projects we are working on,” he added to his reply.
He later revealed that the IOHK team is building its own Chrome extension and he had some questions about the delisting. He added that the company has “eight engineers working on it.”
Considering that MetaMask plans to add Ethereum Classic in the near future, it wouldn’t hurt for both parties to have a line of communication and cooperation.
Looking at MetaMask’s official statement, we find that the team behind the project is seriously concerned with its discovery of clones of its extension meant for phishing.
“This proved to be an interesting wake-up call for a majority of our team. What was left when one searched the term ‘MetaMask’ on the store was a few re-branded MetaMask forks and one ambiguously branded lookalike,” the team wrote.
The rest of the statement suggests that the MetaMask team wants to make its “ongoing battle” against phishers a priority and hopefully help browser developers clamp down on fake extensions.
This article appeared first on Cryptovest