ConsenSysDiligence / ConsenSysDiligence/vscode-ethover
Allow usage without an API key if using a custom API
Open
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
If using an API like Routescan (eg `https://api.routescan.io/v2/network/mainnet/evm/43114/etherscan/api`), usage without an API key is actually allowed under a certain limit, since you only get an API key if you go for the paid plan.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the VS Code extension handles a custom API URL and decides whether an API key is required. Check the behavior for the Routescan example in the issue, then verify that a custom API can be used without a key within its stated limit while existing keyed usage remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100