Please enable JavaScript.

Coggle requires JavaScript to display documents.

TodayQ - Coggle Diagram

- - - - attributes for user : on backend
        active trade
        RPT
        APT
        ATS of/on
        Binance key
        associated analyst key
        a/c balance
        trade balance
  - - - Analyst will see all coins listed : Our system will fetch the market rate of that coin as soon as the admin enters the name and show the real time price with order quantities available
        coinmarketcap api/ or others
        No candle sticks as of now
        Requirement : Real time view of all coins
        
        Take trade by clicking on individual coin
        All the users associated with analyst
        Make a trade from the particular analysts server using each of the users api key; time taken = ?
        
        Process of taking trade:
        Variables that we need? What are we sending?
        Coin, buy rate/range, sell rate, stop loss, analyst key, risk percentage, timestamp
        function will run for each user - > need APT passed before making trade for each user, if no field passed use max value (90% of the ac balance) , run only for users RPT > given by the analyst per trade
        .
        edit functionality / Cancel trade -> how to make this atomic? if apis are initiated we will need another request? - > Solved
        edit means -> cancel the whole order and place new
        check order status
        api.get_order(symbol=pair,orderId=orderId)
        api.cancel_order(symbol=pair, orderId=order_id, origClientOrderId=client_order_id)
        
        After trade is done, should be saved for order history.
        Users who received the trade?
        Ratings calculation formula for analyst?
        update user balance after successful request response cycle
        
        Analyst handle engine:
        analyst key
        Key -> fetch user data ; redis
        
        Trade taking engine:
        Coin, buy rate/range, sell rate, stop loss,
        
        APT thing & RPT calculation:
        After one loss, a/c balance will be made 0, now when trade is made, balance will be cut from apt, keeping the Risk percentage in mind.
        APT & RPT calculation is done real time , on every trade basically and will be updated on admin and analyst panels.
        use only APT & RPT
        
        Big problem here = bulk trades?
        How can we pull this off? Multi-threading? multiple instances for binance requests?
        
        Lead
        
        if analyst is controlling a lot of money, he can add that to many coins
        
        Admin can change ongoing trades. see the total amount. This is like the master analyst. Control all analyst. Take trades for whole pool of users. Cancel on going - trades as well
        hierarchy of order & user
        
        Admin can control the Auto trading on off etc. if he turns it off all account with ATS will get notif and will be told ats is under maintenance. if under that time, some new users sign up and start auto trading, he will not be able to do so. We can also display maintenance messages on the page of ATS in the app.
        Limitation = on-boarding will be hindered? which means we need ATS on/off toggle in app instead of while on-boarding.
        
        On the analyst panel, the admin will see the total no. of subscribers and their sum of APTs. All user info of all analysts and control of all panels.
        Our system will fetch the market rate of that coin as soon as the admin enters the name and show the real time price with order quantities available. - > Real time trade taking window coins requirement
        
        Put this ATS thing where user is putting binance key
    - - for all that we have users order id, whatever response we get on that order id, like order completed or all, we will send the notification right to that particular user but his balance will be updated according to the complete trade that’s happening for all user.
        
        frequency of notification : ?
        why would user know ?
- - - - Think of edge-cases