It should also use any USD the holder has in their balance instead of being forced to buy on the open market at a premium.

and why is that not happening ?

I didn't mention bitshares for two reasons. First I haven't reviewed the technology in bitshares 2. I haven't seen formal technical documentation nor have I looked at the code. Second, I have to review the license structure. I remember when bitshares 2 was announced it wasn't under a proper FLOSS license. I cannot recommend a technology that is owned by or controlled by a single entity.

You can not ignore a blockchain that is on the top 7  blockchains the last 2 years... Mentioning a technology doesn't mean you are recommending it! Your answer feels so pathetic... 

Discussed this with @svk already, but I don't want this to get lost in translation.

Please bundle the webwallet for local use! In fact, no need to maintain windows/linux light wallet builds if you have a universal browser version in my opinion!

so we add only our local API connection?

...which is?

When a margin call is triggered, the collateral will be used to buy any of the asset that's available for sale cheaper than [feed price * maximum short squeeze ratio] to cover the position.

I think max squeeze short is 10% (from 50% it was) so it is more possible that on a thin market like now it will not find on the open market all the bitAsset needed to close the position... In that case will the system wait like on bts1 until the price feed is in a range of 10% from the price feed and find the remaining asset's? What happens if the price never comes back to the price range it can collect the remaining assets?

I definitely think 10% must increase soon so the market will define the "fair" prices and the exchange  will not be so much feed depended... less vulnerable to feed manipulation... can we find the sweet spot?
can the system automatically increase the squeeze protection spread when for example the 24h volume is high and decrease it when the volume is very low?Make it sense?

Is it safe when active key is the same with the owner key?

Take 80% of the fees (burn 20%) and when you reach 100 BTC (yep, not 75 BTC!)
then make the transition to 50:50 as your initial plan was....

PS  I am serious, People are tired to fund projects that never deliver what they are promise.If you are confident for your product you have nothing to fear! The  soonest you deliver the sooner you will get your profit's.
PS2 And then yes, I believe it will be successful and will find big support (traders) ...
PS3 You can make the transition even after you reach 150-200 BTC...
     

Quote from: xeroc on October 19, 2015, 09:03:27 am

Quote from: lzr1900 on October 18, 2015, 09:59:24 pm

Quote from: Pheonike on October 18, 2015, 09:58:14 pm

Hit the borrow button in top right under the on the exchange tab.

borrow the bitassets and buy BTS?

no .. the other way round .. you borrow bitUSD (or bitCNY ...) using BTS as collateral

Both are correct... or am I wrong? 

1) Opening a short:
You borrow "the bitasset", "bitUSD" (using BTS as collateral) and then buy BTS (AKA sell borrowed "bitasset" for BTS)

2) Closing a short:
You buy back what you borrowed, hopefully for less BTS than you sold it for,  and hit the "close" button on account view to give "the asset" back to the blockchain

3) Profit?
If you (1) sold higher than you (2) bought back, you have more BTS than before step n°1 
If you (1) sold lower than you (2) bought back, you have less BTS than before step n°1 

Hope it helps 

 

sure it helps!

I someone has already imported his bts1 private keys to the hosted bts2.0 openledger web-wallet and he decides to import them to a desktop full node or desktop light-client, how can he delete his private-keys  on the hosted wallet so he can be sure he is not in danger of a future server compromise? Deleting the wallet is enough?