Quote from: clockwork on December 20, 2018, 09:41:37 am

Quote from: bitcrab on December 20, 2018, 09:38:32 am

Quote from: clockwork on December 20, 2018, 09:07:28 am

I seriously think it's time to return settlement offset to 1% and I believe it will also play a part in reducing bitCNY premium

(as well as bringing consistency among bitAssets)

no, it will help to reduce discount if there is, helpless to reduce premium.

I believe bitCNY market is now in a state where it works in the opposite way.

0.95 of bitCNY value (i.e. what it can be settled for) is considered = 1 CNY and thus traders are trading 1 bitCNY as >1+ CNY leading to premium.

IMHO that is part of the reason why bitCNY over the last couple of months prior to BSIP42 always had a greater premium than other bitAssets.

5% offset  make 1.05bitCNY considered 1 CNY if feed price = market price.

Quote from: clockwork on December 20, 2018, 07:51:15 am

Quote from: alt on December 20, 2018, 07:07:43 am

Quote from: xeroc on December 20, 2018, 07:01:12 am

Quote from: alt on December 20, 2018, 06:57:33 am

Quote from: clockwork on December 20, 2018, 04:51:54 am

Which version client are you guys using?

I have tried almost 10 different "stable" versions recently published,
but almost no one can be used in fact
I wonder who are the manage of the GUI development worker, too bad.

Bug reports can go here:
https://github.com/bitshares/bitshares-ui/issues/

no thanks.
I thought we should pay for a professional worker.
I wonder who can tell me which version is really usable.

you can either keep dissing the worker or help make it better, your call

If you don't provide details/bug report it can't be fixed

(fwiw, mine runs with 15 different accounts loaded and appears to work fine)

There are 2 possible reasons for your problem:

a) There was a change recently on the subscription behaviour of bitshares-core. Copying from teh release notes:

"Operators of API nodes that service client software that expect to receive updates about all data on the blockchain by default (such as BitShares Reference Wallet before 180401), as opposed to narrowly subscribed data, should ensure that their API nodes are configured with the enable-subscribe-to-all set to true due to Pull Request 1049."

So maybe you're connecting to an API node with the subscribe-to-all setting set to true

or

b) This issue recently brought up by abit: https://github.com/bitshares/bitshares-core/issues/1472

Interestingly, neither of those is a UI issue but core API issues identified and fixed (for (a)...application depends on node operator)  or in the process of being fixed (for (b))

So please don't spread false accusations.

can you tell me which stable version do you use?
when I met a problem, I try to change another version, almost every stable version has different problems after I try less than  several minutes.
I think there are no need to report bug for such unstable software, they need to test themself, it's a job with payment, not a hobit job.

for the issue brought by abit, it's also the GUI's job of course, they used a wrong design, used a wrong api.
when I tell the wallet that my account is alt, it just need to subscribe infomation about alt, I never told it to subscribe other account with the same key.
eventually, it even bring those junk account to my default list of transfer function. such stupid.

The POLL is NO CONSENSUS.

You are BREAKING ALL RULES AS WITNESS !!!!!!

You have no right to change MSSR without creating a worker which will get voted in.

I will make sure that all witnesses which will change MSSR without a REAL community consensus will lose their voters.