What is a BerylBit RPC?
An RPC endpoint connects wallets and applications to BerylBit. Use the endpoints above for JSON-RPC requests, and keep alternatives available for regional endpoint failures or rate limits.
Chain ID 9012 · BRB
BerylBit
Public RPC endpoints and wallet configuration for BerylBit.
Network endpoints
Add BerylBit to MetaMask
Use “Add to wallet” to request the network configuration. Always verify chain ID 9012, currency BRB, and the selected RPC before approving.
Public RPC safety
Public endpoints are third-party infrastructure. They may log requests, enforce limits, or become unavailable. Never place private keys, seed phrases, or secrets in an RPC request.
Common RPC errors
Rate limits, browser CORS rules, network mismatch, and temporary provider failures are common. Try another listed endpoint and verify the returned chain ID.
BerylBit RPC FAQ
What is the RPC URL for BerylBit?+
https://mainnet.berylbit.io is the recommended endpoint in this directory. Multiple alternatives are listed above in case an endpoint is unavailable from your region.
What is the BerylBit chain ID?+
BerylBit uses chain ID 9012 (0x2334 in hexadecimal).
How do I add BerylBit to my wallet?+
Use the Add to wallet button above. Your wallet will ask you to review and approve the network details.
Are public RPC endpoints safe?+
Treat public RPCs as infrastructure operated by third parties. They can observe requests, rate-limit traffic, or be unavailable. Never send private keys or seed phrases to an RPC.
Found an issue?
Report a broken RPC →Help keep network data current through a community contribution.