more BSCSCAN_TOKEN#1062
Merged
iamdefinitelyahuman merged 1 commit intoeth-brownie:masterfrom Apr 17, 2021
Merged
Conversation
iamdefinitelyahuman
approved these changes
Apr 17, 2021
Member
iamdefinitelyahuman
left a comment
iamdefinitelyahuman
left a comment
There was a problem hiding this comment.
Looking at the diff history, I don't think this is a regression - it was just never added. Guessing bscscan recently modified something in their API due to an increase in requests?
Contributor
|
yep, that's my bad. I am using |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What I did
I found a spot where we were still using ETHERSCAN_TOKEN instead of BSCSCAN_TOKEN.
How to verify it
Checklist