SEO Title: Redbelly Network Developer Troubleshooting: Fix Common RPC, Wallet, Gas, Deployment & EligibilitySDK Errors Description: A practical troubleshooting guide for Redbelly developers covering recurring RPC, MetaMask, transaction, gas, deployment, contract verification, testnet funding, and EligibilitySDK integration problems.
Network: Redbelly Testnet Testnet RPC: Testnet Chain ID: Currency: Testnet Explorer: Redbelly's current developer environment identifies Testnet as chain ID with the canonical RPC endpoint above.
Table of Contents Quick Reference Index Before Troubleshooting Network and RPC
1.
Routescan API Returns 429 Too Many Requests
2.
RPC Endpoint Times Out or Does Not Respond
3.
Wrong or Outdated Redbelly RPC Endpoint
4.
Chain ID Mismatch
5.
JSON-RPC Error Before Wallet Activation Wallet and MetaMask
6.
MetaMask Does Not Detect Redbelly
7.
RBNT Appears on Explorer but Not in MetaMask
8.
Ledger + MetaMask Returns Internal JSON-RPC Error Transactions and Gas
9.
Insufficient RBNT for Deployment
10.
Cannot Estimate Gas
11.
Insufficient Contract Balance
12.
Nonce Too Low
13.
Transaction Remains Pending Smart Contract Deployment and Verification
14.
Hardhat Deployment Uses the Wrong Network
15.
Contract Verification Fails EligibilitySDK
16.
EligibilitySDK Package Cannot Be Installed
17.
Missing REDBELLY_API_KEY
18.
EligibilitySDK Test Credential Faucet Is Unavailable
19.
Local EligibilitySDK Callback Does Not Work
20.
Developer Cannot Determine a Wallet's On-Chain Eligibility Verification Matrix Community Validation Sources and References Quick Reference Index Error / Keyword Likely Cause Jump To Routescan API rate limit #1 / Endpoint, network or service issue #2 Outdated endpoint #3 / / Network mismatch #4 Account/network/transaction configuration #5 MetaMask cannot find Redbelly Network not configured #6 RBNT not visible in wallet Token/network configuration #7 Ledger + MetaMask Hardware-wallet/RPC/network issue #8 Wallet lacks RBNT for gas #9 Transaction would revert or required state is invalid #10 Contract lacks required RBNT/value #11 Stale or reused transaction nonce #12 / stuck transaction RPC, nonce or replacement issue #13 Hardhat deployment failure Wrong network/configuration #14 Contract verification failure Wrong chain, compiler or constructor settings #15 / / package unavailable GitHub Packages authentication #16 Missing verifier API credential #17 Test credential faucet Demo credential faucet unavailable #18 / callback failure Mobile wallet cannot reach local server #19 / KYC Eligibility integration uncertainty #20 Before Troubleshooting Always confirm the environment first.
Redbelly Testnet Check the RPC directly: Expected result: is hexadecimal for chain ID .
Network and RPC
1.
Routescan API Returns 429 Too Many Requests Symptom The explorer API returns: A Discord developer reported: Another developer independently reported that Routescan was repeatedly rate-limiting API requests.
Root Cause Routescan applies request-per-second and daily call limits.
A means the API limit has been exceeded.
Routescan currently documents a keyless free tier of 2 requests/second and 10,000 calls/day.
A registered free API key increases this to 5 requests/second and 100,000 calls/day.
Solution Reduce request frequency and implement retry backoff.
Example: For applications making frequent API calls, use a registered Routescan API key and send it in the header: Routescan recommends backoff/retry or a higher-limit plan when the limit is exceeded.
Prevention Cache explorer/API responses.
Do not poll continuously when event subscriptions or longer intervals are sufficient.
Implement exponential backoff.
Use a registered API key for applications with sustained API usage.
Never expose an API key in frontend code.
2.
RPC Endpoint Times Out or Does Not Respond Symptom Typical symptoms include: or a request simply hangs.
Root Cause Possible causes include: Incorrect RPC URL.
Temporary network/service interruption.
Local proxy/V