256
Stakeholder Proposals / Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« on: August 16, 2018, 06:13:58 am »
Voted
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.
I think this is a problem that price feed scripts should address, rather than proposing to somehow change from median(price feeds) to max(price feeds) within the bitshares core.
If price feed publisher's scripts are overly reliant on BTC:BTS prices then they should be upgraded to sample multiple exchanges, accounting for trading volume (flagging suspected centralized manipulation) and sampling from many more alternative trading pairs such as USDT, ETH, mutliple internal bitshares market references (feed|market)..
With Max, if a single price feed publisher publishes 1000000 (or some other very high feed) then it would cause global settlement, where as median price feed would have been more secure from such an outlier price feed.
recently there are a lot of price feeding relevant discussion on Chinese community and wechat groups https://bitsharestalk.org/index.php?topic=26909.0
summarizing the discussion and reviewing what happened in the market these 2 days, I suggest witnesses to adopt a new model for CNY price feeding:
suppose A = BTS price in bitCNY at DEX + bitCNY deposit fee, Bi = BTS price in CNY got from one big external exchanges.
feed max(A,B1,B2...) as the BTS price in CNY.
let me explain why suggest to do so:
there are always shorters who watch the whole market, the dept positions in DEX everyday, and they are clear about the margin called rules in DEX, so when bear comes, they begin their work: sell BTS in big quantity in centralized exchange and lower the fee price and make the big debt position margin called, and they buy the margin called orders to make profits.
surely there should be shorters exist in a healthy market, but it's not good to always encourage shorting and speed up the falling of BTS price in bear market. to cultivate the smartcoin ecosystem, it's necessary to continually optimize the rules to encourage longers and discourage shorters.
the target CR is a very good new feature to do so, but we still need more optimization.
external centralized exchange are not transparent enough, in some market like zb.com, user can borrow BTS and short, and price come from these exchanges are mostly coverted from in BTC to USDT and then CNY, the too long conversion chain involve many uncertain factors.
BTS/bitCNY pair in DEX is the BTS trading pair with highest volume on the earth, and bitCNY has a convenient channel to fiat CNY, so this price can answer exactly in what a price people can buy/sell BTS in fiat CNY.
sometimes the price in one market can be temporarily lower or higher then other markets, if the finally adopted price temporarily higher than the actual price, it lead to little problem, but if the finally adopted price is temporarily lower than actual price, it may lead to margin call which should not happen, this is why I suggest to feed max(A, B)
currently the fed price to DEX comes from centralized exchange, it is like the neck of DEX are grabbed by exchanges outside DEX, we should let DEX itself play more important role in price finalizing, let the longers and shorters fight in DEX, not other exchanges.
to be careful, I suggest only try this model in CNY price feeding at first.
Also, if you find the easter egg, let me know.
Hi everyone,
Website is live: https://hackthedex.io/
If you have any issues, questions, or feedback, let me know.
We can adjust rules as need be, so let's discuss what's best for the community.
Also, if you find the easter egg, let me know.
As a witness I would like to suggest add a "Witness Key" to update signing key and publish price feed only.
_____________________
- I've personally tried to use best of my networking knowledge and create a pattern on the globe to utilize maximum availability. We did first (and only) public node in Australia and Canada, covered from East to West Coast of USA (where last year was only Xeldal and broken Texas node - before movement of witnesses re bitcrab vote and requirement) and all i'm saying we really had careful picks not just random purchases. I intend to keep utilizing network and optimizing its costs.
- I would point out that ES node that we would be hosting through worker has only sense having home in USA and best ISP for it would be Privex.io - Alex (Clockwork - Witness) is hosting ES in Asia and Fabian (Xeroc - BBF) is hosting ES in Europe.
Thanks for original input and feedback and hope to read more from you on this. Very important topic indeed, since we got into the problem with finance from scalability issues.
Charge the security deposit from the asset. the security deposit should be 888bts at least, to curb the fraudulent and phishing asset.
when someone create a asset,the man need to pay the security deposit to active the asset every year, the security deposit is circular, when paid the new security deposit, then return the old security deposit.
when the asset didn't renew the security deposit timely,then forbid the trading of this asset;
if the asset didn't renew the security deposit two years,then the DEX can confiscate the security deposit.
One cool thing about increasing the network's cut on transaction fees is .... wait for it ... the users are not affected. They pay 100% anyways. The only ones impacted are basically
* openledger, who claimed that referral fees are not their business
* cryptobridge, who seems to make money by listing fees and trading
* other frontends that may come with their own assets just like OL and CB
* bitshares europe, which sofar only has referral fees as income (as it's owner, I would rather see BitShares grow than hold back rational business decisions out of pure and stupid greed)
Sounds like a good idea.
Thanks Abit for sharing your thoughts on this WP. I hope that other proxies & committee members follow your lead to come forward and express their support or concerns publicly about this initiative.
That is something that should have been requested and started PRIOR to launching the worker proposal on-chain so you could tweak it before putting it up for voting. (and no, a few hours, at least as far as the forum post is concerned does not constitute "PRIOR")
Prior evaluation happened, but mostly in their telegram. I voiced mine there, if anyone cares I happily repeat them.
Sounds like a good idea.
Thanks Abit for sharing your thoughts on this WP. I hope that other proxies & committee members follow your lead to come forward and express their support or concerns publicly about this initiative.