-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
feat/ add ETCswap V3 and V2 connectors #340
Conversation
@chris-mercer Fyi, v3 connector basically adds concentrated lp functionality which is what I've done. However, if you insist, I'll gladly make changes as requested to fulfil this bounty. Just know the connectors will most definitely have issues down the road. |
@chris-mercer Also, resolve necessary comments/requests |
No i don't insist. If you followed the pattern in the repo then thats perfect. I noticed the chain was not named correctly and wanted to make sure there wouldn't be any issues on the naming. I'm not as familar with the code base as you. Thanks for addressing the issues that made sense. |
hi @vic-en Could you please check branch conflicts? |
Steps:
Actual: Expected: logs_hummingbot.log
|
…nto feat/etc_swap_v3
@nikspz All updated. |
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.
Ethereum Classic's testnet is Mordor, not Goerli.
https://chainlist.org/chain/63
Recommended Funded Endpoint: https://rpc.mordor.etccooperative.org
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.
@chris-mercer The point of replacing that url is to prevent calls to the default endpoint.
Workflows shouldn't access external services except in special cases.
@vic-en please create PR to add
Test performed:
|
@nikspz hummingbot/hummingbot#7159 |
Test performed:
https://etcerscan.com/address/0x930a6f15DA31912c0D0f3819D932E3397Cc1d410 |
@nikspz The price says 0. What fee tier are you using? |
|
@nikspz There are just 2 pools for that pair. LOWEST and MEDIUM |
LOWEST: Failed to add liquidity, Client stuck on WARNING - etcswapLP_ethereum-classic_mainnet connector is not ready. Please wait... MEDIUM: |
@vic-en Could you please check failing tests? |
If you're using etc.rivet.link as the rpc endpoint, nothing should be affected in your work. The v3.etcswap.org app does not interact with the archival node/subgraph at all. The info.etcswap.org archival node is messing with the subgraphs ability to read new events. This is entirely different and simply related to that display app of activity (charts, volume, recent trades). I mentioned this in case you are using that for visibility into your actions. Again, ETCswap V3 is entirely functional: v3.etcswap.org |
@nikspz @fengtality I'm kind of confused on where we are on this bounty. What are all the blockers here and what are the steps to get our network participants able to build the ETC/USC market for V3 with HB? I noticed this is open too: hummingbot/hummingbot#7159 |
…nto feat/etc_swap_v3
…into feat/etc_swap_v3
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.
Test performed:
- Cloned PR7159 + gwPR340
- Installed Client and gateway PR
- Reviewed gateway ONLINE
- Curl:
- Etcswap connector
- wallet/add: ok
- /chain/status: ok
- /chain/tokens?chain=ethereum-classic&network=mainnet: ok
- /chain/allowances: ok
- /chain/approve: ok
- /wallet/remove: ok
- /amm/price: ok
- /amm/trade: ok
- Etcswap connector
Pending:
- EtcswapLP
- Amm_arb strategy
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.
Test performed:
- Cloned PR7159 + gwPR340
- Installed Client and gateway PR
- Reviewed gateway ONLINE
- Curl:
- Etcswap connector
- wallet/add: ok
- /chain/status: ok
- /chain/tokens?chain=ethereum-classic&network=mainnet: ok
- /chain/allowances: ok
- /chain/approve: ok
- /wallet/remove: ok
- /amm/price: ok
- /amm/trade: ok
- Etcswap connector
- EtcswapLP
- wallet/add: ok
- created/started amm_v3_lp strategy successfully
- review position id matched with exchange
- amm/liquidity/add: ok
- amm/liquidity/position: ok
- amm/liquidity/collect_fees: ok
- amm/liquidity/remove: ok
- Amm_arb strategy
- created/started amm_arb strategy using etcswap_ethereum-classic_mainnet
- review rate oracle issue related to USC token not available on rate oracle sources (binance and etc.)
- changed tokenname from USC to USDC
- started new amm_arb strategy using etcswap_ethereum-classic_mainnet and kucoin
- review filled orders for both connector_1 and connector_2: ok
Please test ETCswap V2 and ETCswap V3 protocols as @vic-en mentioned this PR addressed both bounties. You can find charts for WETC/USC markets in GeckoTerminal now. https://www.geckoterminal.com/ethereum_classic/etcswap-v2/pools |
…nto feat/etc_swap_v3
@nikspz I've resolved conflict. |
Steps:
Actual: review rate oracle issue related to USC token not available on rate oracle sources (binance and etc.) |
@nikspz I changed them to USDT. They should work now. |
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.
-
Cloned latest Feat/add ethereum classic hummingbot#7159 gwPR340 (fb11f32)
-
Installed Client and gateway PR
-
Reviewed gateway ONLINE
-
created/started amm_arb strategy using etcswap_ethereum-classic_mainnet and binance successfully
-
Reviewed forced USDT-USC 1 Rate oracle ✔
-
amm_v3_lp strategy: ok ✔
-
Curl:
- Etcswap connector
- wallet/add: ok
- /chain/status: ok
- /chain/tokens?chain=ethereum-classic&network=mainnet: ok
- /chain/allowances: ok
- /chain/approve: ok
- /wallet/remove: ok
- /amm/price: ok
- /amm/trade: ok
- Etcswap connector
-
EtcswapLP
- wallet/add: ok
- created/started amm_v3_lp strategy successfully
- review position id matched with exchange
- amm/liquidity/add: ok
- amm/liquidity/position: ok
- amm/liquidity/collect_fees: ok
- amm/liquidity/remove: ok
Hi @vic-en |
|
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
hummingbot/hummingbot#7110
Tests performed by the developer:
Tips for QA testing: