Repository navigation
Fixing the guidedStart #18
Description
The guidedStart allows a user to quickly get started with different bots and strategies on the Rubicon Market. The current implementation is bricked and breaks at multiple places. The end goal of this is to have a complete working implementation of guidedStart that lets a user
- Create a MarketAid if they do not have one or connect to an existing instance
- Run the market-making bot
On master the guidedStart doesn't get to the first prompt. But on the allAboard branch, the flow currently looks like:
- What type of bot would you like to run
- What strategy would you like to employ
- Network (does not include Polygon networks)
- Market aid (If I say that I do not have a market aid, it crashes)
Steps
1. Add options for other networks
2. Add the npm run aid functionality to the Market Aid in case a user does not have an address
Metadata
Metadata
Assignees
Labels
No labels
Activity
ishandhanani commentedon May 24, 2023
Currently I have the address generation inside of the
userMarketAidCheckCallbackfunction. This works but there's also a way to add it tostartGenericMarketMakingBot. This will require changing up the resolve inside the 'userMarketAidCheckCallback' and adding logic to handle it.The
MarketAidgeneration does not take long but it would be good to create ahelpUserCreateNewMarketAidInstancethat holds the logic. This will make it easier to change when the TODOs are addressed inmarketAid.ts