Committee proposal to re-enable force settlement

[wackou]

I think wackou has another price feed script (don't you? @wackou ).

I encourage someone else to come up with an alternative price feed script so we can get some diversity. 

^^ This!

I do have another feed script, yes, that is slightly different from xeroc's. I haven't updated it, yet, however it was less far off before given that I already included btc38 and bter (yeah, I know, that was before they became blatantly crappy...), weighted by volume. I plan to add other exchanges, too, when I get the time. Was fixing other things first, but the feed script is next on my todo list. Please follow this thread for updates: https://bitsharestalk.org/index.php/topic,19537.0.html
I have an update coming right after the next update of the bitshares client (there's some required functionality that will only be available with next version)

[xeroc]

I encourage someone else to come up with an alternative price feed script so we can get some diversity. 

^^ This!

[tbone]

I missed that post from bytemaster.  And cryptofresh doesn't seem to indicate who created the proposal.  It would have been nice for committee members to be explicit about this as their rationale for quickly voting the 20%-->2% change, otherwise it looks to stakeholders like you're not being deliberate enough, especially after the previous controversial proposal that was voted through.  Anyway, it looks like things are falling into place.  Thanks.

Thanks for your feedback.
Off topic, I think your inputs on GUI are really important and valuable. Can you look into new GUI and make comments on here or github?

OT:

I'm very pleased with the progress on the UI, especially this latest release.  But yes, I plan to provide additional feedback as soon as I have a chance!

[cube]

The proposal to resume 'Settle' operation is voted in unanimously (with 100% support from non-inits) by the Committee.

[clayop]

I missed that post from bytemaster.  And cryptofresh doesn't seem to indicate who created the proposal.  It would have been nice for committee members to be explicit about this as their rationale for quickly voting the 20%-->2% change, otherwise it looks to stakeholders like you're not being deliberate enough, especially after the previous controversial proposal that was voted through.  Anyway, it looks like things are falling into place.  Thanks.

Thanks for your feedback.
Off topic, I think your inputs on GUI are really important and valuable. Can you look into new GUI and make comments on here or github?

[tbone]

I missed that post from bytemaster.  And cryptofresh doesn't seem to indicate who created the proposal.  It would have been nice for committee members to be explicit about this as their rationale for quickly voting the 20%-->2% change, otherwise it looks to stakeholders like you're not being deliberate enough, especially after the previous controversial proposal that was voted through.  Anyway, it looks like things are falling into place.  Thanks.

[clayop]

Update: after theoretical has confirmed that GRAPHENE_DEFAULT_FORCE_SETTLEMENT_MAX_VOLUME is indeed set to 20%, the committee has worked with the devs to create another update asset proposal to change the value to 2%.

We set the expiredate to the same as the other proposal, so both parameter changes will go live in roughly 14 hours from now.

You can review the proposal here: http://cryptofresh.com/p/1.10.21
Thx to @roadscape for quickly adding this new view!
Thx to @theoretical for reacting so quickly and creating the asset proposal!

Why is this being done so quickly without much discussion here?  Has @bytemaster even indicated whether this setting was intended to be 2% or 20%?

2%

Where did he say that?  I have no strong feelings about this setting one way or the other, but I think we need to stop making such rash decisions.

https://bitsharestalk.org/index.php/topic,20356.msg262600.html#msg262600

And please be advised that this change is started from the the devs (as a patch). init0 created the proposal.

[tbone]

Update: after theoretical has confirmed that GRAPHENE_DEFAULT_FORCE_SETTLEMENT_MAX_VOLUME is indeed set to 20%, the committee has worked with the devs to create another update asset proposal to change the value to 2%.

We set the expiredate to the same as the other proposal, so both parameter changes will go live in roughly 14 hours from now.

You can review the proposal here: http://cryptofresh.com/p/1.10.21
Thx to @roadscape for quickly adding this new view!
Thx to @theoretical for reacting so quickly and creating the asset proposal!

Why is this being done so quickly without much discussion here?  Has @bytemaster even indicated whether this setting was intended to be 2% or 20%?

2%

Where did he say that?  I have no strong feelings about this setting one way or the other, but I think we need to stop making such rash decisions.

[clayop]

Update: after theoretical has confirmed that GRAPHENE_DEFAULT_FORCE_SETTLEMENT_MAX_VOLUME is indeed set to 20%, the committee has worked with the devs to create another update asset proposal to change the value to 2%.

We set the expiredate to the same as the other proposal, so both parameter changes will go live in roughly 14 hours from now.

You can review the proposal here: http://cryptofresh.com/p/1.10.21
Thx to @roadscape for quickly adding this new view!
Thx to @theoretical for reacting so quickly and creating the asset proposal!

Why is this being done so quickly without much discussion here?  Has @bytemaster even indicated whether this setting was intended to be 2% or 20%?

2%

[tbone]

Update: after theoretical has confirmed that GRAPHENE_DEFAULT_FORCE_SETTLEMENT_MAX_VOLUME is indeed set to 20%, the committee has worked with the devs to create another update asset proposal to change the value to 2%.

We set the expiredate to the same as the other proposal, so both parameter changes will go live in roughly 14 hours from now.

You can review the proposal here: http://cryptofresh.com/p/1.10.21
Thx to @roadscape for quickly adding this new view!
Thx to @theoretical for reacting so quickly and creating the asset proposal!

Why is this being done so quickly without much discussion here?  Has @bytemaster even indicated whether this setting was intended to be 2% or 20%?

[BunkerChainLabs-DataSecurityNode]

Dear community,

Today, we tested the new version of xeroc's price script and have fine-tuned the configuration and the reported CNY price is VERY close to the real counterpart. All other asset prices have been improved too. Thank you very much to @cube @Bhuz and @xeroc for spending so much time yesterday and today for making it possible!

All witnesses have been instructed to upgrade to the newest pricefeed version.

This means we can finally re-enable the force settlement function and have done so in http://cryptofresh.com/p/1.10.19

Best regards
mindphlux

PS: Committee members who support this motion, please post here as well.

datasecuritynode has updated to the latest feed script by @xeroc.  for his dedication and hard work.

Happy to see this supported. I would have preferred it not had happened at all. What's done is done now.

Vote for BunkerChainLabs-com for Committee Member if you would prefer to see things done differently.

[cube]

Voted.

I was dead beat after yesterday's intensive testing.  The tests went on for 2 days now.  The testing and tuning turned out to be more complex than original thought.  Many thanks to xeroc for patiently listened to our numerous feedbacks and offered his kind advice.  This is in addition to the tremendous effort and time he has put in into refactoring, architectural change and developing the fix. Bhuz is meticulous in his testing too.  This is a great team to work with!

I am glad the improved price feed script is ready and going into production with the witnesses.   bitCNY is back on track. Other bitasset markets  have improved too. All the hardwork is paying off.  It is a nice feeling to start a new day. 

[JonnyB]

I encourage someone else to come up with an alternative price feed script so we can get some diversity.

I'm not too techinical but bitreserve uphold provides this api call to get all trading pairs other than bts

https://api.uphold.com/v0/ticker

[alt]

let's see if our selfless Chinese Whales Committee members are going to vote for this.

what should you do if selfless Chinese don't do this?will you cry? my little baby
I ask to disable the forum admin from this kid

this is shameless alt, I did not know you are an idiot.

don't you hear taunt from him?
I have repeat many times, puase the settlement is not for Chinese,
so why he always give the noise, talk about Chinese?

as a committee, I do what I think it's right,
I don't do it for satisfied all people,
and I found it's true, most people don't have any judgment, they just follow BM

I'll re-enable force settlement before we correct the limit volume to 2% from 20%.
it's related issue, and there will be a security problem if we re-enable force settlement with limit 20%

if you think I'm wrong, just vote me out.

[clayop]

I think wackou has another price feed script (don't you? @wackou ).