Fix dead Blast RPC URLs in README setup docs - #27
Merged
Conversation
Blast's public Starknet RPC has been decommissioned and now returns a JSON-RPC error instead of connecting. Swapped both README references (sepolia setup snippet, mainnet fork instruction) for the Alchemy endpoint this repo already ships in packages/snfoundry/.env.example. packages/nextjs/app/vesu/page.tsx:69 has the same dead URL but is left untouched here since it's already modified by the open fix/step-3-frontend-and-cairo-test PR.
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
Blast's public Starknet RPC endpoints have been decommissioned (see PR #23 on
basefor the full trace). Replaced both README references with the Alchemy endpoint this repo already ships inpackages/snfoundry/.env.example. Identical fix to #23/#24/#25/#26 (byte-identical diff, verified), so the cascade merge stays a no-op..envsetup snippet):RPC_URL_SEPOLIA— blastapi → alchemyyarn chain --fork-network ...— blastapi → alchemyOnly the URLs changed.
README.mdis excluded from the scaffold-stark-2 sync workflow, so this is the only channel available to fix it.Not included, deliberately:
packages/nextjs/app/vesu/page.tsx:69also has a dead Blast URL, but that file is already touched by the open PR #22 (fix/step-3-frontend-and-cairo-test) — left alone here to avoid a conflicting edit. The Blast faucet reference (a different, live service) is untouched.Proof
Replacement Sepolia endpoint verified alive:
Test plan
git diff --stat— README.md only, 2 lines changedbasebranch fix — identicalpackages/nextjs/app/vesu/page.tsxuntouched (rides with PR Fix stale @starknet-react/core imports and cairo test arity mismatch #22)