I just installed your app, looks neat!

I have clicked around, but I could not see how you actually collect your prices for the assets? Where can I find that information?

We are still investigating what the cause is there. But one.thing we see its likely not a problem with performance at the backend because the servers were basically bored, even through such heavy "out of sync" periods. It might be an issue with client/server connection management.

The cause needs to be identified, setting up your own node is treating the symptom (but of course us a work around atm)

I understand that concern, but driving decisions through fears will not get us further. Of course, a negative statement would have atomic impact, but the legal council that was chosen has experience and necessary contacts there.

At some point regulators will come looking again, the more BitShares grows the more likely. Bittrex is just the first who needs a legal opinion. What's the alternative? Just waiting and hoping no one will notice BitShares?

I would say this worker is a much needed pro-active action!

Quote from: sschiessl on February 05, 2018, 09:58:56 am

Quote from: abit on February 04, 2018, 04:55:19 pm

This issue will be addressed by fixing https://github.com/bitshares/bitshares-core/issues/343 .

In short,
* always update the call price after a short position got partially margin called, and
* always start matching from position with least collateral ratio.

With this logic, if a big position is partially called by a small limit order, the position will leave on the book with higher call price. It can still be fully called by a big limit order though, which is at same risk as small positions.

This will very likely resolve most of the issues, yet one enables to buy the whole margin call. I think that hurts the BTS price when the whole market is going up. Clever traders can bet on the markets rising (all cryptos are connected in that somehow) and simply buy the whole margin call order without driving up the BTS price accordingly, which is bad for all BTS holders.

I think some mechanic should be added to avoid buying the whole order if a collateral ratio of e.g. 2.00 can be achieved by partial selling (of course making sure in the formula that you can buy the whole order if the ratio is e.g. less than 1.5 or something). I would be happy to support working out a proper mechanics for this issue if there is agreement. Nevertheless, just fixing the above issue is also very beneficial.

I think it's possible to implement a mechanism that only minimum required collateral is sold, to archive a given collateral ratio, the MCR (175%), or perhaps another parameter that a little more than MCR to avoid dust data (orders/fills).

However, under certain circumstances (to stop loss for example) traders want to be fully magin called and/or don't want the call price to be updated. The demands are fair to some extent.

So, this is a serious question: what mechanism is better for the ecosystem? I'm not sure so far.

If that second parameter can be optionally set by the user when creating the position (e.g. must be 2.00 or higher), you have both options and you dont kill the logic of existing positions (they would be handled as a position with the parameter left blank)

I agree that big margin calls have a significant impact on the market, there is room for improvement.
Are there any mechanics in the fiat world to learn from / compare to?

Anyways, I like your approach, but.it.seems overly complicated, but maybe there is thought in it that I can't grasp yet, I am in no position to qualify your proposal. Could you explain more why you wanted two parameters?

Anyways, the first thought that came to my head is to introduce a fallback collateral ratio (can be set optional by the user when creating the position, to not break existing logic, must be e.g. 1.85 or higher) . The mechanic would be as follows:
 If a position is margin called, an order is placed to sell as many BTS as needed to reduce the debt, such that the position has a collateral ratio higher or equal to the fallback ratio after the sale.
This introduces also a implicit reserve and enhance part but utilizes only one parameter.

Definitely claim your BTS!

One of the posts here should help you https://bitsharestalk.org/index.php/board,45.0.html

How is your system setup?

Is this all installed?
http://docs.pybitshares.com/en/latest/installation.html