-
-
Notifications
You must be signed in to change notification settings - Fork 246
(feat) move ethereum token lists to conf
#126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@cardosofede for this to work when users install Gateway using Docker, I think the lists stored in I tried to do this in the last commit, but the JSON files are still not being copied over. |
|
I changed the Dockerfile and created this PR in the deploy-examples repo: hummingbot/deploy#19 Tips for QA
|
|
PR update:
Test macbook pro (m1)
Test WSL ubuntu 20.04LTS
Pending:
|
|
Docker using the Hummingbot+Gateway example from this PR hummingbot/deploy#19 Steps:
Actual: Exit the Client and tried to connect wallet again - successfully connected, however still no lists folder created, Failed to ran amm_arb / approve tokens (on development branch same command approve tokens successfully/ amm_arb showing profitability on dev) |
|
@nikspz Did you see this line in the new instructions in the deploy-examples README? Populate Gateway lists folder from token lists from the Gateway image: |
|
Was able to replicate Ralph's issue on Source (amd64)
|
|
@david-hummingbot I changed the If you see that the When the tokenListSource is When the user is running from source, the |
|
We should add Steps: Actual: Expected: |
david-hummingbot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docker
- initial test using hummingbot/hummingbot:scripts-copy image - ok
- test using deploy-examples PR#19 - ok
- Docker image built locally - ok
- docker compose up -d
- sudo chmod -R a+rw ./hummingbot_files
- docker cp hummingbot:/home/hummingbot/scripts-copy/. ./hummingbot_files/scripts/
- verified scripts files are present in the /scripts folder
- docker attach hummingbot
- run start --script and made sure scripts are showing - ok
- run script - ok
Source install
- install gateway ok
- run
./gateway-setup.sh, no errors - checked
ethereum.ymlfile and verifiedtokenlistsourceshowsconf/lists - checked
conf/listsfolder and .json files are present - start up gateway and client shows online
- gateway connect uniswap arbitrum
- run
gateway config ethereumand confirmtokenListSourcedirectory
@nikspz For bash scripts, we previously only supported "Y" or "y" - see https://github.com/hummingbot/gateway/tree/main/docker. I think we only try to support |
A description of the changes proposed in the pull request:
src, Docker users have been unable to easily add new tokensconf/[list].jsonsrc/templatesgateway-setup.shso that it creates all files from templates directory, including the new listsTests performed by the developer:
I tested this with a random Arbitrum new token: https://arbiscan.io/token/0xBfbCFe8873fE28Dfa25f1099282b088D52bbAD9C
Added token info to Arbitrum list in

conf/listsPostman returns a 0 balance for EQR - if no token is found, it would not return a value

Hummingbot client (after restarting) also shows EQR balance

Tips for QA testing: