EVM Network Information
Essential information about the Injective EVM network
Injective EVM Mainnet Details
Chain ID:
1776
JSON-RPC Endpoint:
https://sentry.evm-rpc.injective.network/
WS Endpoint:
wss://sentry.evm-ws.injective.network
Faucet: N/A, to obtain Mainnet INJ see
injective.com/getinj
Explorer:
blockscout.injective.network
Explorer API:
https://blockscout-api.injective.network/api
More Providers
Explorer - Blockscout mirror:
injective.cloud.blockscout.com
JSON-RPC - Quicknode
quicknode.com/chains/inj
Note that you will need to create an account on quicknode to obtain an endpoint URL
Permissioned
After the EVM Mainnet launch, there will be an initial permissioned period. During this period, developers will need to whitelist address(es). To do so, join the Injective discord, then comment in this discussion.
Injective EVM Testnet Details
Chain ID:
1439
JSON-RPC Endpoint:
https://k8s.testnet.json-rpc.injective.network/
WS Endpoint:
https://k8s.testnet.ws.injective.network/
Explorer:
testnet.blockscout.injective.network/
Explorer API:
https://testnet.blockscout-api.injective.network/api
More Providers
Explorer - Blockscout mirror:
testnet-injective.cloud.blockscout.com/
Tokens
wINJ (wrapped INJ) -
0x0000000088827d2d103ee2d9A6b781773AE03FfB
USDT (MTS USDT) -
0xaDC7bcB5d8fe053Ef19b4E0C861c262Af6e0db60
Note that this follows the MultiVM Token Standard, which means the same token can be used in all Injective modules (EVM, Cosmos) without using a bridge.
For more information about Injective EVM Testnet see the following pages:
Last updated