Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
faq [2019/04/05 16:00] profitview |
faq [2019/04/05 16:06] profitview |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| <panel title="4) - How much do the OCC & Multipass Indicators cost?"> | <panel title="4) - How much do the OCC & Multipass Indicators cost?"> | ||
| - | OCC & Multipass are each offered at an annual cost of 0.1 BTC per year. | + | OCC & Multipass are each offered at an annual cost of 0.1 BTC per year. |
| </panel> | </panel> | ||
| Line 144: | Line 144: | ||
| At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''retries=<number>'' only to that line of your syntax. | At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''retries=<number>'' only to that line of your syntax. | ||
| - | **Note:** According to the [[https://www.bitmex.com/api/explorer/#!/Order/Order_new|BitMEX API documentation]] close orders are reduce only by default, so for ''c=position'' commands there is **NO NEED** to specify ''r=1'' – with the benefit of these closing orders being exempt from load shedding while "reduce only" orders can fail! | + | **Note:** According to the [[https://www.bitmex.com/api/explorer/#!/Order/Order_new|BitMEX API documentation]] position closing orders are considered "reduce only" by default, so for ''c=position'' commands there is **no need** to specify ''r=1'' – with the added benefit of normal closing orders being exempt from load shedding while "reduce only" orders can fail! |
| </panel> | </panel> | ||