Skip to content

Injective Helix đŸĨˆ

🛠 Connector Info

  • Exchange Type: Decentralized Exchange (DEX)
  • Market Type: Central Limit Order Book (CLOB)
  • Maintenance Tier:
  • Maintainer: InjectiveLabs

Currently, Injective is a Silver exchange, as voted by HBOT holders in each quarterly Epoch. This means that Hummingbot Foundation maintains the components below via Bounties, tracking improvements made to the Gold exchange connectors of that type.

Component Status Notes
🔀 Spot Connector ✅ Supports testnet
🔀 Perp Connector ✅ Supports testnet
đŸ•¯ Spot Candles Feed Not available
đŸ•¯ Perp Candles Feed Not available

ℹī¸ Exchange Info

🔑 How to Connect

Create a wallet on one of the supported networks below:

Chain Networks
injective mainnet, testnet, devnet

The connector supports two different account modes: - Trading with delegate accounts - Trading through off-chain vault contracts

There is a third account type called read_only_account. This mode only allows to request public information from the nodes, but since it does not require credentials it does not allow to perform trading operations.

Delegate account mode

When configuring the connector with this mode, the account used to send the transactions to the chain for trading is not the account holding the funds. The user will need to have one portfolio account and at least one trading account. And permissions should be granted with the portfolio account to the trading account for it to operate using the portfolio account's funds.

Trading permissions grant

To grant permissions from a portfolio account to a trading account to operate using the portfolio account funds please refer to the script account_delegation_script.py

Mode parameters

When configuring a new instance of the connector in Hummingbot the following parameters are required:

  • private_key: the private key of the trading account (grantee account)
  • subaccount_index: the index (decimal number) of the subaccount from the trading account that the connector will be operating with
  • granter_address: the public key (injective format address) of the portfolio account
  • granter_subaccount_index: the index (decimal number) of the subaccount from the portfolio account (the subaccount holding the funds)

Off-chain vault mode

When configuring the connector with this mode, all the operations are sent to be executed by a vault contract in the chain. The user will need to have a vault contract deployed on chain, and use the vault's admin account to configure this mode's parameters. To know more about vaults please read the official Mito managed vaults documentation

Mode parameters

When configuring a new instance of the connector in Hummingbot the following parameters are required:

  • private_key: the vault's admin account private key
  • subaccount_index: the index (decimal number) of the subaccount from the vault's admin account
  • vault_contract_address: the address in the chain for the vault contract

🔀 Spot Connector

Integration to spot markets API endpoints

Order Types

This connector supports the following OrderType constants:

  • LIMIT
  • LIMIT_MAKER
  • MARKET

🔀 Perp Connector

Integration to derivative markets API endpoints

Order Types

This connector supports the following OrderType constants:

  • LIMIT
  • LIMIT_MAKER
  • MARKET

Position Modes

This connector supports the following position modes:

  • One-way