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 Defira connector #5422
feat/Add Defira connector #5422
Conversation
Add Defira gateway scaffold w/ correct ABI
…nectors-api feat/Add Defira to `GET /connectors` API
Feat/Add Defira mainnet tokens to config
Add correct Defira testnet DEX address
Rename Defira connector, fix testnet router address
Add @types/node-fetch dev dep
…hema Feat/Add Defira config schema and init code hash
PR Update: Upon testing we have noticed that an
Steps to reproduce:
|
@arnelhbot Are you sure this is related to my PR? I didn't make any changes to the Harmony chain aside from the gas price calculation and the |
Hi @navneethjayendran yes, looks like it has something to do with Harmony chain and outside of the PR. We are investigating this atm since this is the first PR connector for the Harmony chain. |
PR Update: Up testing we noticed that when starting the
Steps to reproduce:
|
@navneethjayendran To fix the current error that @arnelhbot faced. You need to add defira to the validated spenders in the |
Thanks for the reminder. I forgot to test this step E2E. Added unit test coverage. |
PR Update: Upon testing, we have noticed we are still getting the same
Steps to reproduce:
|
@Faouzijedidi1 It seems like the Harmony chain integration is problematic since things are failing on operations that have nothing to do with the connector, e.g. reusing an existing wallet. Can we meet and discuss the best solution to these issues? |
Upon testing new updates, we are getting a
Steps to reproduce:
|
@arnelhbot I see the problem. There are red herring validators for the Harmony chain that don't actually do anything. I edited the spender validator there instead of the actually used Ethereum validators. It is now fixed and I am able to do AMM_ARB with Defira against itself. |
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 Feature branch with no issues
- Created Docker image in gateway folder
- Generated-cert and gateway create with no issues
- Successfully connected Defira mainnet/testnet
- Created simple AMM_Arbitrage strategy and started bot
- Confirmed arbitrage opportunity and filled order
- Txhash visible in ledger
- History confirmed displaying order filled
Bring in Defikingdoms changes
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 Feature branch with no issues
- Created Docker image in gateway folder
- Generated-cert and gateway create with no issues
- Successfully connected Defira mainnet/testnet
- DefiKingdoms visible as a connector
- Created simple AMM_Arbitrage strategy and started bot
- Confirmed arbitrage opportunity and filled order
- Txhash visible in ledger
- History confirmed displaying order filled
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
Tests performed by the developer:
Tips for QA testing:
as needed or switch to the Defira testnet tokens JSON in
harmony.yaml
)