Let's assume it is possible to get a SBD/USD price feed. How would the blockchain use it to determine how much STEEM to produce via conversions?
You are viewing a single comment's thread from:
Let's assume it is possible to get a SBD/USD price feed. How would the blockchain use it to determine how much STEEM to produce via conversions?
If you have a live conversion rate for STEEM/USD and also for SBD/USD (without assuming that 1 SBD = 1 USD) (or alternatively a BTC conversion rate rather than a USD conversion rate) - then you can calculate the appropriate amount of STEEM to create accurately and simply by:
Amount of Steem to Create = (Amount of SBD To Convert * SBD/USD Ratio) * STEEM/USD Ratio
So in other words, just work out how many USDs the SBDs are really worth (not assuming they are 1:1) and then work out the amount of STEEM needed to match the USD value. It would be possible to do this without involving USD at all since major exchanges also convert STEEM/SBD by BTC too.
As long as there's no assumption that 1 USD = 1 SBD then there's no problem. Or did i misinterpret the OP and there actually isn't an assumption made in the calculation that 1USD = 1SBD?
If this assumption goes away though, then what is the point in having SBD? If we are going down that route, then why not just get rid of SBD entirely, pay users 100% in STEEM (50% SP, 50% liquid) and skip the whole conversion process?
Well, yes - if SBD isn't actually fixed to USD then it has little function.. I think @ned was quoted as saying words to the effect that SBD isn't really so great for this reason. Personally, I would get rid of SBD - but as long as it exists, there's no need to have this conversion error in the system.
Well the current situation with conversions is not really an error - at least in my opinion. The blockchain rules say that if users convert 1 SBD, they will get "approximately one USD worth of STEEM". That is actually working, even today with the higher SBD prices. The problem is that users can get more than that, and by doing the conversion - they are missing out.
I understand your perspective, but I use the word error in such situations in the sense that even if the software matches the spec, there is an error from the perspective of the user and thus also an error in the thinking used to define the spec. User experience is the driver for functionality in a successful business system, as opposed to 'adherence to documentation'.
I am not in disagreement on that. The main reason I submitted the PR :)
:)
Yes, a warning is the least we can do!