Setting up your Ethereum wallet¶
Why does Hummingbot need my Ethereum wallet private key?¶
Strategies that transact on decentralized exchanges (such as Radar Relay, Bamboo Relay, and Dolomite) directly interact with smart contracts on the Ethereum blockchain. Therefore, transactions must be signed and authorized, which requires your private key.
connect ethereum to connect your Ethereum wallet with Hummingbot.
Enter your wallet private key >>>
Importing your wallet¶
There are two ways to import your Hummingbot wallet from other wallets like Metamask and MyCrypto:
- Importing the wallet's keyfile (recommended)
- Importing the wallet's private key
Using a wallet that is available in your Metamask (i.e. importing a wallet from Metamask) allows you to view orders created and trades filled by Hummingbot on the decentralized exchange's website.
To import your wallet using its JSON keyfile:
- Export the JSON keyfile from other wallets such as Metamask, MyCrypto, or MyEtherWallet
- Save the file in the
- Rename the file to
[address]is the public Ethereum address in the format
- Start Hummingbot
connectcommand to confirm if keys are confirmed and added for ethereum.
- In the Hummingbot client run command
- Ether the private key associated with the wallet
When you import a wallet with Hummingbot, a JSON file named
key_file_[address].json is created in the
/conf directory. This JSON keyfile contains the encrypted private key of your wallet and can be imported into other dApps.
Within the Hummingbot CLI, you can use the
export_private_key command to display the private key associated with a wallet address. You can import your wallet to dApps like Metamask and MyCrypto using this private key as well.