People who already hold HBD can sell it immediately and initiate a conversion to get it back (with an expected profit) in three days. That's an interesting point, but I admit I'm a bit concerned that a

Also, no matter how often witnesses update, currently the median is only updates once per hour. That would either need to be changed, or you would need to use individual witness updates rather than the

Yes, I agree.

This is one of those type of changes that we really can't judge the impacts of with certainty until we make it and release it into the real world. So practically speaking, I don't think there will be any

Everything you've said here I generally agree with, but I think you wrote this prior to my last comment, so just to note as per my last comment, the reason I favored this over the 3.5 day delay method

I don't really know what the real interest level in such things are. Yield chasing definitely does seem to be a thing right now, but it's not something I'm keen to work on, I'd rather work on other things

I guess the issue is I was assuming that witnesses will publish any adverse price move during the last hour (including at the current time). In such as case, I don't believe it can be gamed. If they aren't

As a side note, one way to prevent downward failure of the peg would be to implement an additional mechanism for creating HBD via Hive collateral. But that's a much more complicated mechanism, and I think

This proposal isn't meant to address downward failure of peg, but that hasn't been much of problem, since HBD holders tend to increase conversions to Hive as haircut is approached. But if the concern is

there will be situations when the backward looking average higher than the current price I added the worst case price in the last hour term in the formula to prevent just this issue.

Are you suggesting an interest bearing account for Hive (similar to what has been previously proposed for HBD)? It's certainly possible to implement, although it's non-trivial and would be a new source

Yes, but once the haircut rule is reached, there's an additional reason why HBD value should drop: it's no longer pegged to at least one dollar worth of Hive.

Effectively, yes: all the Hive that's getting converted is being burned, so more Hive is being burned than the equivalent amount of HBD that is being created.

I wonder if we could plausibly modify the frontends to give helpful tips about ways for someone to improve the SEO value of their posts. For example, in this case, it could alert them when their images

I'm sure that's likely the case, that's why I'm proposing something very simple to do.

Open-sourcing of code is not a beauty contest. And, IMO, there's no need for the code to be "convenient for collaborators" before open-sourcing. The main thing that open-sourcing does is make

Your proposal mentions open-sourcing, but it's not clear on the timeline. Will you immediately be open-sourcing your software, or is that planned for some later time during the proposal period (and if

It sounds like your view is quite similar to mine. While I don't discount the social media rewards aspect of Hive, it is just one aspect, and it shouldn't dominate future development the way it dominated

We'll announce a tentative HF date when we're ready for the public testnet to be setup.

Yes, the fire only cost us about a day of work, and it only impacted our system admins (unfortunately, I was included in that list, and I was up till about 3am last night working on hived nodes for