Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Etherscan V2 API keys #1092

Closed
PaulRBerg opened this issue Nov 21, 2024 · 2 comments
Closed

Use Etherscan V2 API keys #1092

PaulRBerg opened this issue Nov 21, 2024 · 2 comments
Labels
effort: low Easy or tiny task that takes less than a day. priority: 2 We will do our best to deal with this. type: chore Maintenance work. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@PaulRBerg
Copy link
Member

sablier-labs/airdrops#5 (comment)

https://x.com/PaulRBerg/status/1849765766129737964
@PaulRBerg PaulRBerg added priority: 2 We will do our best to deal with this. effort: low Easy or tiny task that takes less than a day. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. type: chore Maintenance work. labels Nov 21, 2024
@andreivladbrg
Copy link
Member

tried to see if it is possible, but i believe foundry has no support for this yet: foundry-rs/foundry#9196

@smol-ninja
Copy link
Member

Can we set a single variable such as ETHERSCAN_API_KEY in .env.deployment.example and then use the same key everywhere in foundry.toml? And when foundry supports it natively, we can switch to their approach.

@andreivladbrg andreivladbrg mentioned this issue Nov 30, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: low Easy or tiny task that takes less than a day. priority: 2 We will do our best to deal with this. type: chore Maintenance work. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@smol-ninja @PaulRBerg @andreivladbrg