BitShares Hangout #22 w/ @chris4210 & @officialfuzzy! - 2017-05-24

chris4210 (66) in bitshares • 8 years ago

Dear BitShares Community,

I want to invite you to our next BitShares Hangout session. We will talk about the latest updates in the Bitshares community, worker updates, business development plans, and other geeky topics all around the BitShares Blockchain.

Topics of this week:

Follow up Consensus 2017
What does EOS means for BitShares?
Latest BitShares Price Development and price adjustments
and more

Join us to discover the next big thing on the BitShares Blockchain!

cheers Chris4210

When does it start?

1 pm Coordinated Universal Time (UTC) or 3pm German time

Who is the host?

Chris4210 + Fuzzy

How to Join

Step 1: Download Mumble Here

Step 2:

Watch Setup Instructions

Step 3:

Enter the following information:

Label: BeyondBitcoin
Address: mumble.beyondbitcoinshow.com
Port: 64738
Username: Enter your username
Password: w0rldCh@NG3rsUN!t3

See you all on the mumble!

You like this post, do not forget to upvote and follow us or resteem

.

bitshares news beyondbitcoin bitcoin

8 years ago by chris4210 (66)

$37.96

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!

Sort Order:

Trending

[-]

cm-steem (67) · 8 years ago (edited)

RE: HERTZ - Optimal smartcoin settings?

What should the "Percent offset of forced settlements" value be for HERTZ?

Considering that the amplitude is 0.5 (50%), the value will fluctuate from 0.5 to 1.5, if someone was to short the asset into existence at the top and they were to hold the asset/debt until the y value was at 0.5, then the asset will be worth 66% less than when they bought it at the top. If we kept the 1% offset for forced settlement then many users would be force settled during each oscillation.

If we set the percent offset to 70% then the fluctuation of the sin wave wouldn't trigger force settlement, only the volatility of the backing asset.

Would there be any repercussions to setting such a high force settlement percent requirement?

Another concern would be whether or not users create tokens with enough collateral to take the change in feed price into account? Users would need to take this into account when they borrow the token into existence.

I've set the max price feed lifetime to 420 minutes, as 7hrs makes for a difference of almost 0.01*Base_reference_asset ($0.01 for example).

Any thoughts on the above? I'd appreciate any input.

CM.