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 - xeroc

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 860
271
General Discussion / Re: Global Settlement for BitUSD
« on: November 26, 2018, 12:09:22 pm »
Since so many in here have no clue about what a global settlement is, let me enlighten you by pointing you to the right direction:

https://steemit.com/bitshares/@bitshares.fdn/how-global-settlements-work

Also, I am not willing to continue support insults and attacks on a personal level. Not against me, nor against any other member of that community. If you disagree with opinions, remove your vote. If you are not happy with how BitShares develops, obtain more voting power or sell and go somewhere else. I know that attacking people is much easier than working out things constructively, it really is.

272
General Discussion / Re: price feeding review
« on: November 22, 2018, 12:17:36 pm »
I agree with @clockwork.
It seems to be an art to find a balance. Certainly we've learned alot from
BSIP42 even though some people in the community declare it a failure
already.

Maybe we can learn the lessons in such a way that it tells us how to use
a dynamic MCR once we have the backend fixed.

273
Stakeholder Proposals / Re: [Witness Proposal] 1.6.129 - zapata42-witness
« on: November 16, 2018, 04:26:21 pm »
+5% for transparency and your work on the price feed script!

274
General Discussion / Re: price feeding review
« on: November 16, 2018, 08:29:20 am »
price feeding is so important for Bitshares and it need witnesses to pay more attention and efforts on this.

witnesses need to publish their algorithm to evaluate and check with the real feed price.

the published algorithm need to include

1. how the premium is calculated out.
2. how the feed price is calculated out based on premium and other factors.

I am sorry that I'll use my voting power to push this thing, after 20th, Nov, I may update voting on witnesses if the behavior on this is not satisfactory. 
I agree with this, assuming that satisfactory == transparent.

This finally leads to requiring more transparency from witnesses and their actions. The times where witnesses just needed to setup "some script" and keep their block producers reliable are over. Competition is heating up and witnesses have to be more pro-active.

I used to have a rather lose set of requirements from witnesses - this will change.

275
As the CTO of blockchain projects, I would like to remind every BTS voter that if they
want this open source framework for mobile apps maintained and improving from
status quo, they need to support the worker that funds that work, otherwise, we wll
have to put our efforts into other projects.

276
General Discussion / Re: suggest to disable forcesettlement for bitCNY
« on: November 13, 2018, 02:43:22 pm »
I'm assuming the vote above is just informative - I guess the Committee have the authority make the decision and if they decide they want to put it to a worker vote on chain they do?
Correct.

277
Technical Support / Re: NOBLE/BTS - There are issues here
« on: November 10, 2018, 08:31:49 pm »
Market fee for NOBLE asset is 100%.
You should have been able to see it in the buy form.
You BTS are gone, sorry.

278
As a community, the easiest way forward would be to appoint *additional* committee members.
No one forces us to stick with the hard-coded minimum of 11, code only prevents us from reaching 1002!

So, community, please apply for committee membership!

279
Graveyard / Re: [Board Removal] Gravity.io - Abandoned project
« on: November 09, 2018, 07:16:48 am »
The forum has a "graveyard" .. i'd recommend move it there instead of "deleting" it

280
General Discussion / Re: suggest to disable forcesettlement for bitCNY
« on: November 09, 2018, 07:16:15 am »
Provided that we need to learn along the way, I think we add another experiment to the game and see if settlements can be dis-incentivized by raising the offset. If that results in a better peg, I am not convinced, but I also don't know.
I feel that the bitCNY:BTS market is the only one that can survive such a (to me rather drastic) step given the liquidity.

As a committee member I have one more request: When a proposal is created and approved for increasing the settlement offset, please make it execute with at least 5 days notice and ensure everyone trading on bitCNY has had a chance to adept to the upcoming change. Thank you.

281
Graveyard / Re: [Board Removal] Gravity.io - Abandoned project
« on: November 08, 2018, 03:11:12 pm »
Well, gravity *IS* a graphene fork. They do stuff and even presented @ GrapheneDev Conference in Shanghai.
Not sure if they use the forums still, but gravity seems legit

282
General Discussion / BitAssets statistics - a start
« on: November 08, 2018, 12:10:42 pm »
I took some of my spare time to learn vuejs and chose to build something
that the community may consider useful:

   http://bitassets.bitshares.eu/

This shows "some" statistics of bitAssets including some charts.

At this point, I am looking for someone that knows Vuejs and can help me
make this page more "pretty". Anyone?

Pull Requests are welcome:
https://github.com/BitSharesEurope/bitassets.bitshares.eu

283
General Discussion / Re: GDEX APP is released!
« on: November 08, 2018, 09:27:04 am »
cool! ++5%

284
General Discussion / Re: suggest to disable forcesettlement for bitCNY
« on: November 08, 2018, 09:08:33 am »
I've foreseen the situation when drafting BSIP42, see
https://github.com/bitshares/bsips/blob/master/bsip-0042.md#uptrend-and-discount
. In short, a static force settlement offset is not quite compatible with
BSIP42 when a bitAsset is oversupplied. BSIP42 aims to let debt position
holders reduce debt at market/fair price, but not at higher price to punish
them. If we agree with BSIP42, we either need to adjust force settlement offset
dynamically, or disable force settlement temporarily.
In fact, I came to the same conclusion. Sorry it took so long.

I think we all agree that BSIP42 leads to force settlement being **overly**
expensive to shorters. I also believe that "disabling" settlement can only
be a termporary solution until dynamic MCR can be used.
Instead of disabling it, why don't we reduce the percentage of supply that can
be settled per maintenance interval to something small? That would discourage
longs from using settlement but would still keep the option open.

I've explained why disabling force settlement is doable in this thread
https://bitsharestalk.org/index.php?topic=27170.0 . I'm not going to explain
again. I'm not going to push anything. It's no fun.

I feel very very disappointed now.
Sorry for that, my fault.

After experimented BSIP42 for 2 months, which has shown obvious effects towards
a tight peg, people still didn't understand the ins and outs, including the
ones who appeared to support BSIP42 (e.g. Fabian @xeroc), not even mentioning
the ones who voted "NO" without even written anything in this forum. All
discussions came to a dead end. No progress. Nothing. Not even a valid
argument. When people just say no but don't tell you why, how you can improve?
We're all 5? It's that hard to discuss rationally? It's that waste of your time
to learn a bit more?
I am sorry to appear reluctant and "slow" when it comes to understanding market
dynamics. As you know, I do not have an economics background. Still, being a
proxy it is a requirement to *understand* what I am doing. Given the amount of
time that I have put into understanding and even defending BSIP42 in the community
makes it odd you are calling me out :-/

OK, some of you asked for a fix for the MCR issue. I've submitted the code (the
fix) to github 2 months before, whoever wants to test it and
push it online can go ahead, or write your own fix.
This is great news, I didn't know that. How can we make sure this
makes it into the next upgrade?

Actually, adjusting MCR is
effectively the same as adjusting price feed + force settlement offset,
so, before the fix is online, we can do something to keep things going,
however, whether to do and what to do also depends on you.
... except that adjusting MCR allows to keep the price feed reflect the 'actual
price'.

Update: Properly punishing debt position owners when a bitAsset is oversupplied
is fine, since it encourages them to reduce supply proactively. From this point
of view, forced settlements can still play a role in the game, although it can
be replaced by forced margin calls. The thing is, target CR doesn't apply when
a debt position is being forced settled, so, not like margin calls which evenly
apply to all positions with (relatively) low CR, force settlements may punish a
few positions too hard, but don't punish other positions at all, so it's IMHO
not a fair enough rule.
I am still trying to figure out if incentives can be aligned for both sides
(shorts and longs) in bearish **and** bullish markets. IMHO, the ultimate goal
is to have a system where merely personal *opinion* about the market leads to
"taking" a side and not market-internal mechanics.

285
General Discussion / Re: Potential Fraud: Need Second Opinion
« on: November 06, 2018, 04:38:05 pm »
What happens here is that the operation 1.11.6737614
uses a override_transfer to send 5000 PEERPLAYS from "flat6" to "c21e6".
That happened on 2016-12-23 13:30:33+00:00 (block #12482277).

override_transfer operations have to be signed by the issuer of of PEERPLAYS (assuming PBSA)

Also, the account has been whitelisted and unwhitelisted before and after the override transfer.
The whitelisting happend onto and off from the account whitelist of the "freedom-ledger" account.
The "freedom-ledger" account is the whitelisting authority for the PEERPLAYS asset.

The "flat6" seems to have traded quite some PEERPLAYS before that happend and also traded STEEM *after* the incident.
There was also a transfer of 30 BTS to freedom-ledger.

If that is fraudulent or not is difficult to tell, but certainly whoever holds the keys for freedom-ledger has signed those
transactions.

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