I. Executive Summary:
Good headway made on the backend integration, thanks in no small part to @Snipermonke01’s python SDK being a pleasure to use. Read functionality is almost complete (say, 75%), with write functionality (placing orders etc) at around 30%; meaning all is on track for the 2 month deadline.
II. Current Progress: Backend:
Bot can now read, parse and filter arbitrage opportunities into the format expected by the architecture, as well as reading data on currently open positions for the user’s account. On the TxExecution side, the bot can now take a universal order object (a small python dict) and parse it out into the format the SDK uses to submit transactions to the chain. Currently being worked on is tx testing and profitability estimations.
Frontend
Frontend has been scoped as follows:
Integratable with browser wallets
Bot interactions handled via a group of buttons at the top of the page corresponding to the console scripts that are currently used to operate the bot in the terminal.
Bottom half of page dedicated to dashboards showing relevant data; profit + loss, historical trades, current opportunities, etc.
Work on the frontend has actually already begun due to the help of a community contributor, detailed further in the next section
III. Community Engagement:
Have been contacted by a contributor who has volunteered to lead the frontend development while I work on the backend integration - which has been great to see.
Additionally, there continues to be a steady stream of what one might colloquially call ‘whales’ reaching out via DM expressing interest in running the bot either personally, or using it as a template to build off of and run as part of a firm. Given that these will be the users who contribute the most to the volume numbers, this is a good sign and was something i was hoping to see as the project reached its current stage.
IV. Partnerships and Collaborations:
N/A, frontend contributor not included.
I. Executive Summary:
Progress delayed somewhat due to falling ill, but nevertheless some important updates have been pushed to the codebase primarily surrounding interfacing with the GMX datastore smart contract.
II. Current Progress: Backend:
Calculating liquidation price turned out to be a tougher problem than originally anticipated; currently reconvening with devs via telegram to nail down the exact calculations. There is some remaining work to be done on adjusting profitability estimations to account for the impact of a given trade size on the funding rate/skew/maker/taker fees, but luckily already have a template of these from other DEXes so its more a case of a refactor than a full from-scratch rewrite.
Bot now has a dedicated GMXMarketDirectory class that, upon initialization, reads all necessary market data from the relevant smart contracts and stores it as a locally accessible object. Also included are a bunch of helper functions that abstract away a lot of the lower level smart contract calls.
Frontend
frontend currently has opportunity visualizations integrated (i.e, it can actively read and display the current market arbitrage opportunities) and focus is now on integrating write functionality; deploying collateral, executing and keeping track of trades and their respective profit and loss, etc.
Am in contact with the dev most days via discord tracking updates and helping with debugging etc, and we meet once a week on mondays for a video call and co-programming session.
III. Community Engagement:
N/A, which is to be expected given current stage of development
IV. Partnerships and Collaborations:
N/A, which is also to be expected given current stage of development.
I. Executive Summary:
Backend 95% completed, frontend ~30%. Have ran multiple successful test transactions.
II. Current Progress: Backend:
Have rewritten large parts of the SDK such that no duplicate smart contract calls are made in the data collection process - managed to get the run time for the demo (i.e, not live trades) version down from 12m20s(!) at the start of the week to 2m10s now, which means that the GMX caller takes about the same as the integrated CEXes, which is really good.
The backend is now waiting on the completion of a get_liquidation_price function that is being built by SniperMonke and is expected to be completed in the coming days. As soon as this is done I’ll be recording a video demonstrating and explaining how the bot works in depth and the backend will be finished.
Frontend
Focus is now on user onboarding experience, there’s a bunch of variables that the user needs to input in order to tune the bot to the users specifications (some of which need to be kept private) so we’ve been designing how best to implement all these.
Some good news is that now that the backend is essentially done I can devote more time to helping the frontend dev integrate all the necessary backend functionality.
III. Community Engagement:
N/A, which is to be expected given current stage of development
IV. Partnerships and Collaborations:
N/A, which is also to be expected given current stage of development.
Test Backend Button Functionality from the Front-end for all exchange pairs.
Using Material-UI for information display
Adding Wallet Adapters instead of using .env
30 to 40% functionality progress.
50 to 60% design and looks.
Now that backend is all ready front-end will be quite fast as less conflict merging and code breaks from backend side.
