Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Bhuz

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 32
271
@tonyk
So, we told that this is a temporary solution, but you don't believe in this statement, right?
That is ok... I don't believe you too when you say that the force settlement will be permanently disabled!

Let's see who is right!

Anybody wanna bet?!

272
@JonnyBitcoin Do you understand that it is a temporary solution?

273
Why don't you campaign to be a committee member so we can have you as a critical voice in our internal discussions? Seriously, please do it, I'd like to have you there.

@Xeldal

I would vote for you, and I am sure that many others would too.

Please consider to propose yourself as a committee member and in this way help, whit your knowledge, the whole community.
(The committee members are part of the community ofc, so to help the community you should help us in making discussions and decisions with your POV)

274
@Xeldal

You actually showed the feed several hours after the committee was informed of the situation.

Your post is from yesterday at 20:00 ish UTC
The committee was informed and checked the feed on 8/9 am of the same day.

At that time the feed was 0.204 while in yunbi there was a price of 0.210, +3%

275
Settlement is not a loophole, and is nothing new.  Its been available since the begining.  it was thoroughly discussed and understood long prior to BTS2 and is a critical function. 

Any available arbitrage opportunity is due to improper pricing of bitCNY by its users/gateways etc.  If transwiser is taking a loss they need to adjust their pricing.  We do not need to change the entire design of bitshares markets to fit 1 gateways uninformed business model.

+1

There is no need to disable the settlement.  If it doesn't already, forced settlement should take all available bids below the feed before pulling from the least collateralized shorts.
+1 +1

Just FYI

Settlement is not a loophole, and is nothing new.  Its been available since the begining.  it was thoroughly discussed and understood long prior to BTS2 and is a critical function. 
The 'loophole' is not referred to the settlement, but to the current situation on BitCNY market.

Any available arbitrage opportunity is due to improper pricing of bitCNY by its users/gateways etc.  If transwiser is taking a loss they need to adjust their pricing.  We do not need to change the entire design of bitshares markets to fit 1 gateways uninformed business model.
No. It is due to a not accurate feed for CNY related markets. This will need a partial refactoring of the pricefeed script by xeroc. He needs time.

There is no need to disable the settlement.  If it doesn't already, forced settlement should take all available bids below the feed before pulling from the least collateralized shorts.
We are asking for a TEMPORARILY disable of the function, just to give enough time to xeroc (for making the changes in the script) and to bitcrab (to put up a liquidity bot).
Plus: seems that the forced settlement doesn't works as you described. Seems that it currently doesn't take the available bids below the feed.


"Current" as in the moment of writing.

Right now Transwiser stop his business, so the situation on CNY is probably different. Still, this doesn't mean that it could not happen again.


276
I stated something wrongly?????

What?

I have not stated that you whant to remove force satelment.... read just what you quoted man...just read it....
as for wrong statement do you want me to quote the OP precisely where it is flat wrong and where it is misleading?

I was referring to what Akado and Xeldad said about "witness should move and solve this" and "blaming it on settlement"

You just ended up in the quote thing :P

277


As already stated the witnesses need a new script to fix the issue.
The script will needs a partial refactoring on how to calculate the feed for CNY related markets.
Xeroc needs time to make this happen.
My feed prices are always a bit higher than others.
Sources of the difference are:
1. I don't pull btc prices from bitcoinaverage but from btc/cny pair of yunbi/btc38.
2. I ignored other btc pairs of btc38 and yunbi

Wish this helps.

Thanks for the constructive reply.

Afaik xeroc plans to pull the prices for cny markets from btc/cny pair of Chinese exchanges (eg. yunbi, btc38, OKCoin) instead of using bitcoinaverage (still used for btc/usd), as you already do!

278
if its a feed issue doesnt it mean ots on the witnesses to solve this? why dont they increase the price by 5% if thats the problem

exactly.  If its a feed issue, witnesses should move to making the proper adjustments.   blaming it on settlement and making radical changes to benefit an uninformed business is not the right approach.
+ 1

Why people doesn't read the whole post and the subsequent clarifications?

As already stated the witnesses need a new script to fix the issue.
The script will needs a partial refactoring on how to calculate the feed for CNY related markets.
Xeroc needs time to make this happen.


What radical changes? We are not asking to remove the settlement, nor are blaiming it as you already and wrongly stated.
We are asking to temporarily disable the function to have TIME to make the needed fix and in the meanwhile stop the "force settle" opportunists.

279
Settlement is not a loophole, and is nothing new.  Its been available since the begining.  it was thoroughly discussed and understood long prior to BTS2 and is a critical function. 
The 'loophole' is not referred to the settlement, but to the current situation on BitCNY market.

Any available arbitrage opportunity is due to improper pricing of bitCNY by its users/gateways etc.  If transwiser is taking a loss they need to adjust their pricing.  We do not need to change the entire design of bitshares markets to fit 1 gateways uninformed business model.
No. It is due to a not accurate feed for CNY related markets. This will need a partial refactoring of the pricefeed script by xeroc. He needs time.

There is no need to disable the settlement.  If it doesn't already, forced settlement should take all available bids below the feed before pulling from the least collateralized shorts.
We are asking for a TEMPORARILY disable of the function, just to give enough time to xeroc (for making the changes in the script) and to bitcrab (to put up a liquidity bot).
Plus: seems that the forced settlement doesn't works as you described. Seems that it currently doesn't take the available bids below the feed.

280
Background
The recent release of GUI wallet introduces a 'Force Settlement' button. This Force Settlement function allows some users to exploit the current 'loophole' in the bitCNY market and gain profit at the expense of the bitCNY providers.
(See https://bitsharestalk.org/index.php/topic,20283.0.html and https://bitsharestalk.org/index.php/topic,20287.0.html)

Transwiser (a major partner who provides bitCNY<->CNY fiat) and a number of Chinese users who depend on this service are suffering big losses.  This is not the worst.  They fear more losses to come.

The Force Settlement function closes the borrow/short positions with lowest collateral ratio and sells their collateral at the settlement price. For the bitCNY market, this means an immediate loss to the shorters (and a gain for the ‘force settle’ users) because bitCNY is trading below the feed price. As we found out, the feed price does not accurately reflect the CNY price.  It is in fact lower than the price listed in major China websites like OKCoin. The price discrepancy created an artificial arbitrage opportunity for the ‘Force Settle’ opportunists.

In addition, the shorters will be forced to sell their collateral even if they have sufficient collaterals to avoid a margin call. 

All this means that the Force Settle opportunists could force settle to exchange bitCNY for BTS on the DEX and then sell them at profit in a centralized chinese exchange eg BTC38.  This HURTS A LOT of bitCNY shorters, no matter the liquidity available in the DEX.

Effectively, they are being forced to sell their collaterals and close their positions against their will.  This introduction of this ‘force settlement’  was not known by the Chinese community at large.  Little wonder that the Chinese community considers this behaviour as ‘robbing the shorters’.


Urgent call for help
bitcrab and alt, representing the Chinese community, called on the committee members for help. After a lengthy and intense discussion (for over six hours), we consider the situation warrants an urgent response as follows:


1) Temporarily SUSPEND the "force settlement" function by raising its fee to 1Billion for about a  week.

This will give us time to put in a remedy:

1) Disable frontend "settlement" button when there are buy orders available above the feed (requires Svk work)
2) Adjust price feed for bitCNY market by including other Chinese exchanges in sourcing CNY prices (xeroc has agreed to work on the changes)
3) Get a CNY liquidity bot to put up buy orders with bids over the feed price and so protecting the shorters from abusing the force settlement function for an opportunistic gain.  ( bitcrab to work on it)

In normal circumstances, the Committee would like to give the Community enough time to discuss the proposals we intend to put up - first with a forum discussion and then setting the proposal period to one week.

As we are facing a crisis now, we would like to ask the Community to support the Chinese’s call for help - and to make this change as soon as possible (within 24 hours) in order to save the Chinese shorters from further losses.

We seek your kind understanding and support for this proposal.

The Bitshares Committee

281
Technical Support / Re: problem with migration to 2.0
« on: November 27, 2015, 12:06:21 am »
I've exported the keys from 0.9.3 c
But i don't think it ever got synced . Could that be the problem ?

Thanks
Did you see all your funds in the 093c client?

If so, it shouldn't be necessary to sync the blockchain.

Do you see your balance when you import the keys in the 2.0 wallet?

282
Another "non-business" fee would be updates of votes/proxies (account_updates in general) ..
being a proxy may turn out to be expensive depending on how many worker and committee movement we will see ..

Maybe we could lower that fee too

-It is not a core business fee
-Nor a big source of income
-It could encourage people to vote
-It would help our proxy members

283
Technical Support / Re: bitshares wallet help
« on: November 26, 2015, 12:58:53 pm »
If the above is correct and I get the same error message, what should I try after that?  Is there anything else or is it at this point I need Xeroc?

I think you could try to install an older version of the bitshares client and see if you can import the wallet there

284
Technical Support / Re: looking for support
« on: November 24, 2015, 10:49:19 pm »
hi,

please let me know if there is free REAL support for recover my funds from old BTS

funds had been missing in open orders after migrating.

after looking for help for nearly 2 month i did not  get a chance to find my funds for free

thanks, appreciate ur help

Let's try again:
Download the fully synced chain folder here: https://mega.nz/#!P8BhCZ4I!NZHkhUEbrgVTNRI1QXhDJI6ly7z1Fv2nFgrpQM1UWDQ

Extract that file. You should find a folder named "chain".
Now go to C:\Users\*your_username*\AppData\Roaming\BitShares
Here you will find another chain folder, rename it as "chain-old"
Copy the downloaded and extracted chain folder and paste it here
Start the 0.9.3c bitshares client

At this point, if you still don't have all the fund, go to the console and try to generate A LOT of keys with:
> wallet_regenerate_keys <account_name> 50000

When the keys regeneration is done, type in the console:
> rescan 1

This could take a long time, just wait and be patient, you can check the scan progress in the bottom left corner.
Once the scan is completed, you should have all the funds.

285
Muse/SoundDAC / Re: Community assistance: Contacting Exchanges to list MUSE
« on: November 24, 2015, 10:39:43 pm »
Btc38 already trades BTS2

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 32