docs: make RPC provider guidance credibly neutral#153
Open
clawdbotatg wants to merge 1 commit into
Open
Conversation
Three small edits so the public skill stops single-vendor kingmaking: - frontend-playbook: "use Alchemy or similar" -> "dedicated RPC provider (Alchemy, Infura, QuickNode, etc.)" - qa: "default Alchemy API key that ships with SE2" -> "default demo RPC key that ships with SE2 (shared across all users, rate-limited)" -- also adds the *why*, not just the rule - testing: replace concrete eth-mainnet.g.alchemy.com URLs in fork-test examples with $MAINNET_RPC_URL, matching the foundry.toml convention the same block already references Left alone (intentionally): - orchestration leaked-key shape example -- real provider URL is pedagogically right - wallets leak-scenario example -- concrete, not a recommendation - indexing -- Alchemy's enhanced APIs (getTokenBalances etc.) are an actual Alchemy product, not generic RPC - tools provider list -- already lists Alchemy/Infura/QuickNode as peers Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
@clawdbotatg is attempting to deploy a commit to the BuidlGuidl Team on Vercel. A member of the Team first needs to authorize it. |
scutuatua-crypto
approved these changes
May 2, 2026
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
2 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.
Summary
Three small edits so the public skill stops single-vendor kingmaking on RPC providers. Found while looking through the skill for places where Alchemy was being recommended specifically rather than as one option among peers.
Changes
frontend-playbook/SKILL.md— "use Alchemy or similar" → "dedicated RPC provider (Alchemy, Infura, QuickNode, etc.)"qa/SKILL.md— "default Alchemy API key that ships with SE2" → "default demo RPC key that ships with SE2 (shared across all users, rate-limited)." Also adds the why (shared, rate-limited), not just the rule.testing/SKILL.md— concreteeth-mainnet.g.alchemy.com/v2/YOUR_KEYURLs in the fork-test examples →$MAINNET_RPC_URL, matching thefoundry.tomlconvention the same block already references.What I deliberately left alone
orchestration/SKILL.mdleaked-key example — using a realistic provider URL is pedagogically right when illustrating what a leaked key looks like.wallets/SKILL.mdleak-scenario example — a concrete leak story, not a recommendation.indexing/SKILL.md— references are to Alchemy's proprietary enhanced APIs (getTokenBalances,getNftsForOwner), which really are Alchemy-specific products, not generic RPC.tools/SKILL.md— already lists Alchemy/Infura/QuickNode as peers +rpc.buidlguidl.comas community option.Test plan
frontend-playbook/SKILL.md:352reads naturally and lists multiple providersqa/SKILL.md:172no longer names Alchemy and explains why the demo key failstesting/SKILL.mdfork-test examples use\$MAINNET_RPC_URLconsistently with thefoundry.tomlsnippet below them🤖 Generated with Claude Code