1
Stakeholder Proposals / Conventions / Coordinating BSIP42 for BitUSD market with MCR algorithm
« on: October 15, 2018, 06:32:50 pm »
A brief discussion took place (https://t.me/BitSharesDEX/329077) on Telegram today where Abit asked about metrics to eval BSIP42 algorithms. I hope to cultivate ideas here on how we can conduct similar experimentation for the BitUSD market as was done for BitCNY last month. Once the core MCR bug is fixed I want to be as ready as I can be to begin these experiments.
I will add to this after I have a look at Zapata's BSIP42 feed code, which I hope to find elements to expose to help us coordinate witnesses' BitUSD feeds.
It would be very useful for any of you witnesses that participated in the BitCNY experimentation to chime in here. I would like to see an explanation of the "experimentation process" that was used for BitCNY. From my observation it was messy and wasn't well coordinated. Nobody could even say with certainty which witnesses were experimenting with BSIP42 and which ones weren't, or how many different BSIP42 scripts were being used by experimenters.
Should witnesses experiment using a "reference" feed script? I think that would be easier to coordinate, and once we've come up with a reasonably stable algo, witnesses can port it or modify it to fit their operation. This is a question, not a foregone conclusion. I will probably use Zapata's script unless something else pops up that would be better.
So one item we could publish here is a list of witnesses that intend to participate in BSIP42 for BitUSD once the core is fixed to allow use of MCR in the algo.
How do we determine when algo "adjustments" are made? IIRC Abit acted as a type of coordinator to inform witnesses about adjustments / premium. Rather than relying on one person lets discuss this so we all know how that is determined so any of us could announce the info. However I think it's better for consistency that only one witness post or pin the announcements.
I will add to this after I have a look at Zapata's BSIP42 feed code, which I hope to find elements to expose to help us coordinate witnesses' BitUSD feeds.
It would be very useful for any of you witnesses that participated in the BitCNY experimentation to chime in here. I would like to see an explanation of the "experimentation process" that was used for BitCNY. From my observation it was messy and wasn't well coordinated. Nobody could even say with certainty which witnesses were experimenting with BSIP42 and which ones weren't, or how many different BSIP42 scripts were being used by experimenters.
Should witnesses experiment using a "reference" feed script? I think that would be easier to coordinate, and once we've come up with a reasonably stable algo, witnesses can port it or modify it to fit their operation. This is a question, not a foregone conclusion. I will probably use Zapata's script unless something else pops up that would be better.
So one item we could publish here is a list of witnesses that intend to participate in BSIP42 for BitUSD once the core is fixed to allow use of MCR in the algo.
How do we determine when algo "adjustments" are made? IIRC Abit acted as a type of coordinator to inform witnesses about adjustments / premium. Rather than relying on one person lets discuss this so we all know how that is determined so any of us could announce the info. However I think it's better for consistency that only one witness post or pin the announcements.