-
Notifications
You must be signed in to change notification settings - Fork 174
margin call price is 150%, not 200% #1273
Comments
@theoreticalbts Can you also confirm whether the 300% collateral claim is true, or whether it is actually 200%? |
300% collateral is currently implemented. I think the intent was always to make margin calls happen when the short side lost 1/2 of their capital, which occurs at 150% when the initial capital is 200% (as it was before the change to 300% / 30 days). |
I think the intent now is to make 200% the call price since that is what is being advertised |
NB, if we implement this, we'll have to grandfather existing shorts into their current margin call prices. We don't want to be in the business of changing the terms of financial derivative instruments after people have already bought them. We have to also consider partial covering. |
Yes, only apply this for future shorts. I don't see why we have to consider partial covers if we do that. |
Someone changed this back. I remember very clearly using *3 /4 as the multiple in prior versions. |
cough c7d7257 cough |
Why was this returned back to 3/4 from 2/3 yet again: 211c5e1#diff-aa03531d90e90a2437e8cba9b668e0ccR400 |
It wasn't changed back to 2/3... it still reads 3/4. |
Yeah, turns out these are both wrong. Suppose you're shorting 100K BTS combined with 50K BTS going long at $0.02 / BTS, the debt is $1000 and the collateral is 150K BTS. The debt's BTS value at price
If margin call happens at 200% collateralization level, you have
which simplifies to
In general when we have collateralization level of
Defining
|
So I will call this |
Ran through the numbers with current order book, this is definitely fixed. Probably by 5fcfef1 |
To be simple, if one shorts 100K BTS combined with 50K BTS going long at $0.02 / BTS, how much should the call price be? It's $0.01 in bts/0.8.x or earlier, but $0.013 in bts/0.9.0 and bts/0.9.1 |
https://bitsharestalk.org/index.php?topic=13453.0;topicseen
The text was updated successfully, but these errors were encountered: