Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Hello, Gitcoiners & Gitcoinerettes! It’s happening again – happy blockchain times are coming to San Francisco 🎉, as the San Francisco…
Heya Gitcoiners & Gitcoinerettes! They say that July is the warmest month of the year (location depending), and we’re definitely getting ready fo…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
### User Story
As a user, I want to be protected from visiting known scam sites in the Status browser.
*Summary*: This is a build on #5801. At the time, we decided to implement only MetaMask phishing detect while [discussing](https://discuss.status.im/t/3rd-party-http-services/437) the addition of more HTTP services, like Google Safe Browsing.
After speaking with our security leads, we feel that the Google Safe Browsing API is a justifiable addition of HTTP reliance and risk exposure.
#### Expected behavior
The [Google Safe Browsing API](https://developers.google.com/safe-browsing/v4/) is used to check URLs navigated in the browser against Google's list of dangerous websites.
#### Actual behavior
Only MetaMask's phishing detect list is used to identify dangerous URLs.