fix: reject ALLOW_INSECURE_RPC on mainnet (H9)#91
fix: reject ALLOW_INSECURE_RPC on mainnet (H9)#910x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
ALLOW_INSECURE_RPC=true bypassed all RPC URL scheme validation including on mainnet. A misconfigured deploy could run mainnet with plaintext HTTP, exposing signed transactions with real funds to MITM. Now throws at startup if ALLOW_INSECURE_RPC=true when NETWORK=mainnet. Devnet usage is unaffected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 15 minutes and 11 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
ALLOW_INSECURE_RPC=truebypassed all RPC URL scheme validation, including on mainnetALLOW_INSECURE_RPC=trueandNETWORK=mainnetTest plan
throws when ALLOW_INSECURE_RPC=true and NETWORK=mainnetdoes not throw when ALLOW_INSECURE_RPC=true on devnet🤖 Generated with Claude Code