What is a Injective RPC?
An RPC endpoint connects wallets and applications to Injective. Use the endpoints above for JSON-RPC requests, and keep alternatives available for regional endpoint failures or rate limits.
Chain ID 1776 · INJ
Injective
Public RPC endpoints and wallet configuration for Injective.
Network endpoints
Add Injective to MetaMask
Use “Add to wallet” to request the network configuration. Always verify chain ID 1776, currency INJ, 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.
Injective RPC FAQ
What is the RPC URL for Injective?+
https://sentry.evm-rpc.injective.network is the recommended endpoint in this directory. Multiple alternatives are listed above in case an endpoint is unavailable from your region.
What is the Injective chain ID?+
Injective uses chain ID 1776 (0x6f0 in hexadecimal).
How do I add Injective 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.