Replace Infura blacklist endpoint
See original GitHub issueThe https://api.infura.io/v2/blacklist endpoint is just a proxy of https://raw.githubusercontent.com/409H/EtherAddressLookup/master/blacklists/domains.json and https://raw.githubusercontent.com/MetaMask/eth-phishing-detect/master/src/config.json. We should request these files from GitHub directly to reduce our Infura traffic.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Replace Infura blacklist endpoint #219 - MetaMask/controllers
The https://api.infura.io/v2/blacklist endpoint is just a proxy of https://raw.githubusercontent.com/409H/EtherAddressLookup/master/blacklists/ ...
Read more >(Notice!) HTTP API endpoint deprecation - Infura Community
With this announcement, Infura is deprecating all APIs accessed via api.infura.io. Support for this endpoint will no longer be provided as of ...
Read more >“Decentralized” ETH Wallet MetaMask And Infura Under Fire ...
“MetaMask relies on Infura as the default endpoint,” Wrote MetaMask, “but this setting can be modified by users if desired, ...
Read more >With the Metamask and Infura blacklisting, it's time to ... - Reddit
With the Metamask and Infura blacklisting, it's time to dump the Ethereum Network, and altcoins at large. First it was Opensea, then smaller ......
Read more >Newest 'infura' Questions - Ethereum Stack Exchange
INFURA is a scalable, standards-based cluster and API endpoint for ... I have a smart contract written in Solidity that stores a blacklist...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We should be able to patch this via #244
Interesting, sending
If-None-Matchworks via cURL:But not via
fetch. 🤔I’m seeing the
If-None-Matchheader being sent but the browser getting a 200 from the server instead of a 304. Can you confirm that the browser sees a 304?