You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can not replicate a single trade as it is too small. min 100$ on Bitmex.
Trading Strategy Proposal:
Upon a change in the trading volume update the position on bitmex accordingly.
e.g. The following query gives all open positions which haven't expired yet. Note, that expired positions although not closed can be force closed at the price at expiry. So we can look at them as being closed at the price at expiry.
select direction, sum(quantity), sum(collateral) from positions where expiry_timestamp >= NOW() and position_state='Open' group by direction;
I assume that the BitMEX position will be posted by the maker not the coordinator.
As captured in #973 I assume that the maker is not concerned about any DLCs just yet, but is just notified by the coordinator about order matches and trade execution success.
That said, I don't think it makes much sense to have multiple "positions" for the same trading pair on the maker. I think the maker should just have a combined position - and if said position reaches enough volume to be hedged on BitMEX then we hedge it. In case the position of the maker falls below 100 again we just stop hedging on BitMEX again.
Note, that expired positions although not closed can be force closed at the price at expiry. So we can look at them as being closed at the price at expiry.
I guess with this you mean that we can just treat them as realised PNL. No need to hedge based on them.
After a position has been opened.
Trading Strategy Proposal:
e.g. The following query gives all open positions which haven't expired yet. Note, that expired positions although not closed can be force closed at the price at expiry. So we can look at them as being closed at the price at expiry.
hint: get inspired by https://github.com/get10101/automaker
The text was updated successfully, but these errors were encountered: