SBD update: Statistical analysis of lower peg and why HF20 has broken SBD even during the good times — Steemit

SBD update: Statistical analysis of lower peg and why HF20 has broken SBD even during the good times

in sbd •  18 days ago

I have given a mathematical analysis of the current lower peg of SBD here.
In that post I had just drawn the lowering of the peg from the risk of changing prices during the conversion by hand. Today I am adding this part from a probabilistic evaluation.

The SBD Lower Peg

SBD can be converted for 1$ of steem. But this only works as long as the marketcap of SBD (assuming a price of 1$) is below 10% of that of steem. Otherwise one steem will not be converted to 1$ but less. The formula for this is simple, and combines a flat curve with a linear drop for low prices of steem, seen by the blue line below.

But the kink in the peg produces an asymmetric risk for people doing the conversion. Let us assume that we are well below 10% debt ratio and the peg is flat. As soon as I do the conversion I know that I will have 1$ of steem at the end, no matter the price fluctuations. This is a working peg and I have a non-risky position.
Let us assume the debt ratio is way above 10%. Now we are in the linear part. When I start the peg, I know that rising prices in steem will give me more $ and falling prices less $. I have a risky position, but this risk is symmetric. If I do not expect consistently rising or falling prices, the random fluctuations will sometimes be beneficial and sometimes harmful. Again the peg is working.

But in-between close to the 10% debt ratio the risk is asymmetric. Let us assume that the debt ratio is just below 10%. Now when I convert 1 SBD and the price of steem rises during the 3.5 day conversion period, I still get 1$ (in steem). But when prices fall the peg is broken and I get less than 1$. Overall, integrating over all possible futures I no longer expect to get 1$, but a bit less. Therefore the peg is not efficient and the real price is a little lower.

I have computed the true peg using the following methods. I assume that the price of steem overaged over the next 3.5 days can be described by a normal distribution around its present day value. Using this model I find the variance using data from the last month. I then average over this distribution computing the expected $ generated by a conversion starting today. This is the real lower peg of SBD and whenever the price is below this value we can expect to make money buy buying steem and converting. Any price above and we expect conversions to burn money.

The present Situation

download (40).png
The lower axis is the price of steem and the upper one the minimum guaranteed value of SBD via conversions. The black line shows the current price. The red dashed line the restarting of printing SBD by the chain.

In blue we see the peg using the current data as a function of steem price (assuming no conversion risk). We see that we are well in the linear regime and a SBD is secured at 0.836$. In orange we have the real peg taking into account the asymmetric risk. At the current price-level both pegs are almost identical since it is very unlikely that the peg at 1$ is fully restored within 3.5 days. It is at 0.833$, only 0.003$ lower than the simplified peg.

We see that we need to go well above 0.5$ steem price in order to properly restore the 1$ peg.
The red-dashed line is showing the price from which the chain will restart printing SBD at full rate, changed in HF20! This means that we will print with a broken peg, taking into account the asymmetric risk of conversions. We cannot expect steem to be valued securely at 1$ even in the future when the markets recover. The old restart of printing before HF20 is shown in the green line, showing a strong peg at 1$ as it should be.

Changes introduced in HF20 are broken and should be reverted as soon as possible!

What To Do

The price of SBD currently at 0.822$ is reflecting the actual peg. Note that SBD does not have an upper peg or a mechanism to push the value down to the lower peg. So there is no easy way to benefit from an overvaluation of SBD. In principle the price of SBD can float above the peg for an indefinite time and we have seen that with 6$ SBD over several months.

But at the current time of rather pessimistic market actors there is really no reason why SBD should be above the peg, only misinformation and misevaluation of its price. I you have any SBD, please note that the peg is broken and you hold a risky asset. The current prices make is easy to get rid of it for a rather good amount of steem and currently conversions are also an option, though not very profitable.


Update: I made a small mistake in my computation and have updated the post to give correct information.

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:  

This post is promoted by @reversed-bidbot as an upvote lottery with a jackpot of 0.498 steem!

Sorry, all tickets have already been claimed.

Excluded from participation are: bidbots, autovoters.

The jackpot is paid in redfish_shares by @curatorbot, giving you lifetime upvotes while supporting the redfish community. Find more information here.

Follow me to also earn steem on my other promoted posts; or use @reversed-bidbot to hold your own raffles. For more details please visit my discord server or read my introduction post

Thanks for the analysis as I had been converting until I saw that the haircut was starting to happen on conversions. If there were a tool to track these changes on a prospective basis using a moving average, it could help give insight to users interested in exercising conversions which ultimately help reduce the supply of SBD and the debt ratio.

Posted using Partiko iOS

·

Absolutely.

Conversions do help with the debt ratio and therefore one may consider still doing them for no profit. But doing them at a loss is a hard sell. I am currently looking at the markets and waiting for the opportunity to buy some cheap SBD for conversion.

Hi @frdem3dot0!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 3.425 which ranks you at #6852 across all Steem accounts.
Your rank has improved 18 places in the last three days (old rank 6870).

In our last Algorithmic Curation Round, consisting of 240 contributions, your post is ranked at #169.

Evaluation of your UA score:
  • You're on the right track, try to gather more followers.
  • The readers like your work!
  • Try to improve on your user engagement! The more interesting interaction in the comments of your post, the better!

Feel free to join our @steem-ua Discord server

I was called to perform a provably fair random drawing for @reversed-bidbot!

There are a 2491 tickets participating in this round.
@sergino holds tickets number 0 - 0
@inversionistam holds tickets number 1 - 8
@frdem3dot0 holds tickets number 9 - 24
@smjn holds tickets number 25 - 129
@freebornsociety holds tickets number 130 - 145
@johnvibes holds tickets number 146 - 148
@builderofcastles holds tickets number 149 - 158
@edgy-ed-morrison holds tickets number 159 - 159
@lovemetouchme2 holds tickets number 160 - 188
@curatorbot holds tickets number 189 - 202
@reversed-bidbot holds tickets number 203 - 210
@warofcraft holds tickets number 211 - 265
@cardboard holds tickets number 266 - 269
@cfminer holds tickets number 270 - 272
@tipu.curator holds tickets number 273 - 281
@knircky holds tickets number 282 - 2490
The merkle root of the block in which this post will appear determines the winner.

·

The block in which the above post is included has a merkle root of 93cdf022b4515f3227798ed3f8ddf1ab2400224d.
To find the winner we:

  1. Convert the merkle root into base 10:
    93cdf022b4515f3227798ed3f8ddf1ab2400224d = 843814214834710831666753440448758860401357103693.
  2. Compute the residual after dividing by the number of tickets: 843814214834710831666753440448758860401357103693 mod 2491 = 254.
  3. This is the winning ticket, held by @warofcraft.

Congratulations!