A follow-up on Web3 Antivirus release, dwelling on how to avoid expensive errors while looking for opportunities.
It keeps happening all the time. You’re browsing through tech communities, Web3 platforms or services, as whoop — you stumble upon a requirement to connect your existing crypto wallet. Why entrust access to your funds right away, before you even know you want to deal with the service? What if it’s about to drain your account?
Sure, this doesn’t inspire a relaxing user experience within Web3, not to speak of impeding the overall adoption progress. Besides, scams and fakes get increasingly inventive, meaning we can all be taken off guard — even DeFi giants experience vulnerability exploits. This got us thinking of a way out, so we heavily researched, coded, test-drived, and finally rolled out Web3 Antivirus.
Phishers knocked on our door themselves
Looks like we didn’t really have a say in that, our mission just chose us itself. While we were busy polishing Web3 Antivirus, we got a sweet email on our Dribbble account. Alongside accolades for the team, there was a job offer involving the creation of an NFT collection.
To assess the page’s current look and feel while giving a rough estimate, we were suggested to check in on a specific website to copy the idea. The P.S. paragraph went: “If you have problems with logging in, you will need to connect in the first window and approve the signature request in the second window. Also, the wallet must have a…
