00GettingStarted

The purpose of this Wiki is to help developers build decentralized applications on top of Injective. Let's dive a bit deeper into each section and explain its purpose so its easier to get the bigger picture.

Note: It is highly recommended to read the Technical Concepts section after reading the overview below. There are some concepts that can have a bit steeper learning curve than others, so we recommend going through them to understand a bit more about Injective.

• Wallets - As Injective is fully decentralized, interacting with the Injective chain requires a wallet connection. Within this section we are going to explain (in technical terms) how Accounts are derived on Injective, how you can connect your wallet straight from the dApp itself and finally have a look at the WalletStrategy - a package built by the InjectiveLabs team which offers out of the box solution for offering multiple wallet solutions to the user to connect and interact with your dApp.

• Querying -

• Transactions - In this section we are going to explore different ways on how to make transactions on Injective. First, we are going to explain (in technical terms) how Transactions work on Injective and some technical concepts around them and then we are going to have a look how to prepare, sign and broadcast transactions on Injective in several ways. There are couple of ways in doing this.

  1. Using the Cosmos native approach in creating a transaction, sign it using a Cosmos native wallet and broadcast it to Injective,
  2. Using the Ethereum native approach in creating a transaction using EIP712 typed data, sign it using an Ethereum native wallet and broadcast it to Injective,
  3. Using the Ethereum native approach in creating a transaction using EIP712 typed data, sign it using a Ledger device and broadcast it to Injective,
  4. Using the Cosmos native approach in creating a transaction, sign it using a raw PrivateKey and broadcast it to Injective,
  5. Using the Web3Gateway microservice - an API which provides fee delegation services.

• Core Modules - In this section we are going to have a quick summary of the core modules on Injective and show examples on how to create some Messages (+ pack them into a transaction, sign them using a private key and broadcast them on Injective) within these core modules.

• Bridge - In this section we are going to have a look at Injective's interoperability and explain how developers can utilize the Peggy bridge and the IBC bridge to bridge assets over to Injective.

• Networks - In this section we are going to have a look at different (pre-defined) available Networks for developers to utilize while building dApps on top of Injective allowing them to start building without the need to make their own infrastructure.

Technical Concepts

Denoms