Skip to main content

​
Fundamentals

Q: What account address types are supported in Injective? A: There are two address types supported:
  • Bech32 (inj...), which is primarily used when interacting via Cosmos wallets/ tools
  • Hexadecimal (0x...), which is primarily used when interacting via EVM wallets/ tools
Q: How can I convert hex addresses to bech32 addresses? Addresses can convert between inj1... and 0x... formats in both directions using getInjectiveAddress and getEthereumAddress from the Injective TS SDK. How to convert between hex and bech32 addresses on Injective. Injective addresses use a bech32 format: inj1.... They are compatible with EVM addresses which use a hex format: 0x.... They share the same underlying public key, and are convertible, 1-to-1 and deterministically.
Q: Is there a way to find which Injective Cosmos address is mapped to which Injective EVM address? A: These address types map to each other through a mathematical operation that is one to one and bidirectional:

​
Infrastructure

Q: When maintaining a private node:
  • Should you store 2.5 TiB of archival data (event provider)?
  • Can you skip that part and make the indexer work?
A: You can prune the event provider. Use the public event provider endpoint for the initial sync, then switch to local deployment from the latest height. Yes, you can skip it. Q: Which network explorer should I use on Injective? Use Blockscout for full EVM compatibility, and use Injscan for full Cosmos compatibility. Specifically, if you are looking for:

​
EVM

Q: Does Injective have a deployment of the multicall3 smart contract? A: Yes, at the following addresses:
Last modified on June 18, 2026