fix(examples): require explicit RPC configuration - #250
Merged
Merged
Conversation
mattsse
force-pushed
the
mattsse/examples-rpc-configuration
branch
from
July 16, 2026 14:35
706ead8 to
2e018c2
Compare
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.
Summary
Why
The shared Ethereum endpoint used throughout the repository is unavailable, so otherwise-correct examples fail for reasons unrelated to Alloy. Public defaults and placeholder credentials are also brittle and make behavior vary by provider.
Impact
Networked examples now use caller-supplied endpoints and fail early with actionable configuration errors. The fallback example accepts at least two comma-separated endpoints. Offline examples are unchanged.
This PR is stacked on #249 so it inherits the compatible dependency lockfile and deterministic CI baseline.