The Osmosis connector determines which routes to take based on the input strategy. In either case, the name of the connector is osmosis_osmosis_mainnet.
The Cosmos ecosystem is a collection of blockchains built using the Cosmos SDK, which communicate with eachother over the Inter-Blockchain Communication protocol (IBC).
Similar to multichain wallets such as Metamask, Cosmos ecosystem wallets come with high interoperability built-in - though specific networks may need to be manually added.
The following are Osmosis-compatible browser-wallets:
Keplr is the most popular Cosmos-based wallet. When creating a Keplr wallet, only users who link a Google Account are able to export their private key directly from Keplr.
To get around this, you can:
Export your Keplr seed phrase.
Restore the wallet using the seed phrase, in a different Cosmos-based wallet (such as Leap wallet) which allows exporting the private key.
Export the private key from the newly restored wallet.
π‘ An Osmosis Private Key has 64 characters
Be aware an exported private key may have an 0x at the start, which may need to be removed to fit the private key format check.
From inside the Hummingbot client, run gateway connect osmosis in order to connect your wallet:
Which chain do you want osmosis to connect to? (osmosis) >>> osmosis
Which network do you want osmosis to connect to? (mainnet, testnet) >>> mainnet
Do you want to continue to use node url 'https://rpc.osmosis.zone/' for osmosis-mainnet? (Yes/No) [default: Yes]
Enter your osmosis-mainnet private key >>>> ****************************************************************
If connection is successful (osmosis-mainnet):
The osmosis connector now uses wallet [Wallet Public Adress] on osmosis-mainnet
Multiple interfaces within gateway/src/amm/amm.requests.ts include additions in the response models and re-use of tokenId > poolId so that when data comes in, the gateway will assume the optional variables relevant for the connector in use; e.g. The interfaces work with both Cosmos and non-Cosmos responses and handle the data accordingly.
From inside the Hummingbot client, run create and then select amm_v3_lp in order to create a custom CLMM strategy.
To select Osmosis DEX, enter osmosis_osmosis_mainnet as the name of the LP connector.
π‘ Only LOW/MEDIUM/HIGH fee tiers available
Inputting 'LOWEST' as the fee tier may result in an error.
Enter name of LP connector >>> osmosis_osmosis_mainnet
Enter the trading pair you would like to provide liquidity on (e.g. WETH-USDC) >>> [Your desired pool pair; e.g. OSMO-USDC]
On which fee tier do you want to provide liquidity on? (LOWEST/LOW/MEDIUM/HIGH) >>> [LOW/MEDIUM/HIGH]
How wide around current pool price and/or last created positions do you want new positions to span? (Enter 1 to indicate 1%) >>> [DYOR]
Enter the maximum value (in terms of base asset) to use for providing liquidity. >>> [DYOR]
Enter a new file name for your configuration >>> [default is 'conf_amm_v3_lp_[#].yml' or 'input custom_name.yml']