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.
https://www.bitshares.foundation/workers/2019-05-wirex-integration
Worker Intent
Months of preparations, intensive phone calls and business development lead to a verbal agreement from credit card processor Wirex to list BTS. We believe that Wirex comes with a reasonable cost-benefit ratio and has an excellent reputation in the space. Wirex comes with 2.2 million registered users and the WirexApp provides access to Euro, British Pound and US Dollar and supports Bitcoin, Litecoin, Ethereum, Ripple, WAVES, NANO, DAI and XLM.
Notably, its debit card services run over VISA.
Wirex is a well established and fully regulated company, properly outfitted with KYC and compliance. All information on its services, terms and conditions can be found on wirexapp.com. Its service also entails an affiliate program and a reward for use. We invite everyone to read up on the details.
We see this as a highly desirable functionality. As BTS is listed on known technical structures we have been offered this opportunity at much less than the usual price.
Depending on their worker load and schedule, Wirex technical team can integrate BitShares within 4 weeks.
just know feed tracker have the full data already,
now you can see the data between 12.26 to 12.31
what a perfect accuracy from crazybit
@stan, now you are the biggest proxy who support crazybit, what's your thought?
here is the full list of top proxy who support crazybit: beos openledger xeroc bitcrab cn-vote clockwork blockchain-bv still abit magicwallet.witness facem-1 spring-team dahu
While tracking the price alone is not the problem, I wonder how he manages to be that accurate and wouldn't even share that with the community.
I've removed my vote (again) and consider keeping it from crazybit unless he explains how he does that.
If the median is manipulated to 0.05 then a will update his feed when he checks next. That's why I said you should *check* frequently.
I admit that in your example the feed would be very much off for a short period of time, which could have catastrophic effects. It is an extreme example though, and I think that in practice such a situation would not occur.
Still, it makes sense to add another rule:
d) if your calculated feed price is off from your published feed price by more than 1-2%, you *should* publish the new price.
in case you don't know how to see the chart, I will tell you the detail:
1. open http://pricefeed-tracker.dex.trading/
2. input crazybit in publisher,
3. input 2018/12/26 10:00:00 am in "From"
4. check the box "feed median"
you will see a chart like below, you can see every 5 minutes(10:15, 10:20, 10:35, 11:00, 11:05, 11:10 etc), the feed price from crazybit will followed the median price.
in fact everytime he refresh the feed price, he always drop to the median price exactely.
other time, they are the same. even at 10:05, when he just changed back from 30% higher price, he droped to the median price exately.
after that, you can try to see other's feed price, you'll know what's the real price from outside should be.
here is a sample from magic wallet.witness, you can see every time he refresh the price, it's random arround the median price.
估计是api变动触发了黑天鹅保护，但是这个保护也失败了，应该喂价10元才对
其它见证人要么根本没保护，要么用的其它APIgdex喂价怎么显示出6.4元了？
脚本问题吧，大概也没设价格防火墙，
gdex喂价怎么显示出6.4元了？
脚本问题吧，大概也没设价格防火墙，
Then I do not understand where you see a problem.a feeds 0.05, b feeds 0.1, c feeds 0.101, then either b or c got a chance to manipulate the median price from 0.101 to 0.05.
If b feeds 0.1 and c feeds 0.101 then it doesn't matter if a feeds 0.06 or 0.09.
It is only important that a *checks* frequently what the price is. Then if b suddenly feeds 0.059, a can update quickly.
In your example a majority of witnesses collude to manipulate the feed price. That always works, independent from what the minority does.nobody manipulate the feed price, they just been supposed to follow your suggestion, didn't update price when it can't change the median price.
这帮见证人简直就是把bts往死里整。
推不动，没办法。
提核心开发BSIP，核心开发者也不会关注也不会了解这些是为了什么，其中涉及到的复杂市场博弈他们也很难想明白，从很早之前的回复来看就知道了。
喂价不得低于内盘实际价格，就是喂价不应当低于投资者在内盘买一个bts所付出的人民币的实际数量。完全合理，合情，合规啊！喂价低于这个值就是不合理的啊，喂价应当反应实际价格啊，这有什么难于理解的呢？现实是喂价竟然长期低于实际价格两个点以上，这不是作恶是什么呢？
应当将喂价的底线写入程序，否则这么任由见证人瞎喂，迟早玩完。
喂价反应的只是一个方面，不过也反应出了BTS现存的一个很严重的一个问题:
这帮节点见证人太他妈的安逸了，很多抵押机制的缺陷已经被市场暴露出了无数次，他们发现不了？！不是发现不了，而是太过安逸，节点竞争的不充分，谁也不想改谁也不想动，你提出问题来，他们会立即反驳没有问题，你提出解决方案来，他们会各种漠视。
一个喂价这么长时间以来难道都没有发现有问题？见证人群体在喂价中权利如此之大，难道不应该负起责任来？！
Is that were we are trying to go with this? Provide frequent up to a minute feeds?
*Publishing* a feed every 2 minutes is normally not required.
*Checking* the feed often is a good idea though. Technically you need to publish only if
a) your feed is about to expire, or
b) if the new feed price would change your position relative to the median (i. e. old price was below median and new price is above, or vice versa), or
c) your feed price *is* the median
You may want to publish more often than that to avoid being accused of neglecting your duties. :-/
I will not support reduce MSSR less than 1.02.
sure we need to keep some profit space for those who help eat the margin call order.
I saw some people want to reduce MSSR because they think feed price is too lower than it should be,
they should try to change feed price instead of change MSSR. there is big different between these two problem.
I agree that price feed problem and MSSR problem are different and need different ways to solve.
but after so long time practice, I think we should understand more deeply on the margin call rule sets.
first, can we just ragard the profit space for eating margin call orders as same as "MSSR-1"?
No, actually when the debt position is margin called/the collateral is forced to be sold, the profit space for eating margin call/the punishment to debt position owners is there.
even if MSSR = 1.
because if you are provided the rights to buy some volume of BTS at the current market price, don't you think this right worth some money?
the same logic that trader need to pay for American options.
and what we can see clearly is that, either we set MSSR=1.1 or 1.02 does not determine whether the margin call orders be eaten or not, the more important factor is market sentiment.
the disadvantage of high MSSR is that, it benefit more on shorting BTS, and then encourage traders to short BTS.
so my ideas on MSSR setting is, MSSR should be greater or equal to 1, the lower, the better.
for bitCNY, 1.02 is a value that do not lead to "margin call orders not eaten" phenomena, it's time to consider to reduce MSSR more, to discourage shorters, to ensure better pegging.
for bitUSD, 1.02 is a value that margin call orders always stay there without being eaten, so no need to consider to reduce MSSR currently.
