fix(onchain): wire BLOCKSCOUT_API_KEY (lost in the #159 merge)#161
Merged
Conversation
Blockscout works keyless, but if BLOCKSCOUT_API_KEY is set it's passed as the ?apikey= query param to raise the rate limit. Keyless path unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The optional
BLOCKSCOUT_API_KEYsupport was committed to #159's branch after it was merged, so it never reached master — the aggregator currently calls Blockscout keyless (works, but ignores the operator's key / rate-limit allowance).This re-applies that one commit: if
BLOCKSCOUT_API_KEYis set it's passed as the?apikey=query param; keyless path unchanged.tscclean.Deploy: rebuild + restart (no migration). Then a configured
BLOCKSCOUT_API_KEYin.envis actually used.