Hey @Customminer great, sounds interesting, would love to learn a bit more about your thoughts behind the oscillation. Do you have some more info on the (fixed) formula and where can I learn a bit more about the Hertz asset? ... what day would be 0% etc. etc. 

@roelandp : Could you please begin publishing price feeds for the 'Hertz' asset? I would massively appreciate your support.

Hertz (Hz) is a Algorithm Based Asset (ABA) which is pegged against the USD and modified to oscillate using a sine wave, thus we are able to create potential phases of buying and selling pressure.

Important Smartcoin settings:

• Maintenance collateral ratio (MCR): 175%
• Maximum short squeeze ratio (MSSR): 150%
• Max feed lifetime: 1440
• Delay for forced settlements (minutes): 720
• Percent offset of forced settlements: 1%
• Min number of feeds: 7

Properties of Hertz (Hz):

• Amplitude: 14% (NOT 33% nor 50% - It was changed to 14% for the first HERTZ asset).
• Period: 28 days.
• Daily price feed change: 2% per day.
• Max price feed rate: $1.14
• Min price feed rate: $0.86

Price feed scripts:

• Reference scripts & calculator: https://github.com/BTS-CM/scripts
• Wackou's 'BTS_Tools' (Only use once pull request #36 is merged): https://github.com/wackou/bts_tools/pull/36
• Xeroc's 'Bitshares-PriceFeed': https://github.com/xeroc/bitshares-pricefeed

http://open-explorer.io/#/assets/HERTZ

Many thanks,
CM.

Quote from: roelandp on December 11, 2017, 08:43:52 AM
Updates!

• SteemFest was great again and with help of the worker we could organise the hackathon as well! Thanks, community, for voting in the worker. Please see https://bitsharestalk.org/index.php/topic,24937.0.html for the full report.


• Just before HF 18 @alt has unfortunately decided to stop btsbots.com and therefore urged witnesses to stop using the btsprice-tool as it used an api for a formatted version of the dex' orderbooks he ran off the btsbots.com domain/node. Personally I was very disappointed as I am a huge fan of the precision and durability (and lightweightness) of his script/tool. Therefore I setup a stack of JSON API-endpoints  (basically static 5 min cached files) mimicking the expected results of the orderbook api which @alt used to have available on BtsBots.com.
  
  • You can find all static api files (cached about 5 mins) here: http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html
  • On this script you can see how I compose the API static files with python-bitshares: https://github.com/roelandp/btsprice/blob/master/docs/btsbot-mimick.py
  • And finally, these are the changes you must apply to support the new url for picking up the orderbooks: https://github.com/pch957/btsprice/commit/3f87e858fa92e6ddd5094e94e511301a32d85728
  Rest assured I hope Alt will some day return to Bitshares!


• With HF18 the black swanned assets have now been revived and I've setup a repo sharing some of the custom pricefeed scripts I use to feed a couple of smartcoins. You can check em out here: https://github.com/roelandp/bts-misc-pricefeeds

Thank you for your trust.

+5%

Updates!

• SteemFest was great again and with help of the worker we could organise the hackathon as well! Thanks, community, for voting in the worker. Please see https://bitsharestalk.org/index.php/topic,24937.0.html for the full report.


• Just before HF 18 @alt has unfortunately decided to stop btsbots.com and therefore urged witnesses to stop using the btsprice-tool as it used an api for a formatted version of the dex' orderbooks he ran off the btsbots.com domain/node. Personally I was very disappointed as I am a huge fan of the precision and durability (and lightweightness) of his script/tool. Therefore I setup a stack of JSON API-endpoints  (basically static 5 min cached files) mimicking the expected results of the orderbook api which @alt used to have available on BtsBots.com.
  
  • You can find all static api files (cached about 5 mins) here: http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html
  • On this script you can see how I compose the API static files with python-bitshares: https://github.com/roelandp/btsprice/blob/master/docs/btsbot-mimick.py
  • And finally, these are the changes you must apply to support the new url for picking up the orderbooks: https://github.com/pch957/btsprice/commit/3f87e858fa92e6ddd5094e94e511301a32d85728
  Rest assured I hope Alt will some day return to Bitshares!


• With HF18 the black swanned assets have now been revived and I've setup a repo sharing some of the custom pricefeed scripts I use to feed a couple of smartcoins. You can check em out here: https://github.com/roelandp/bts-misc-pricefeeds

Thank you for your trust.

Organising SteemFest again. This year it will be in Lisbon, 1/2/3/4/5 November. Many BTS'ers are coming! And now... Adding a Blockchain Hackathon in the mix!

Asking for Bitshares stakeholders to support a (small) worker for sponsorship for promoting Bitshares as a Focus Chain on the hackathon. Please, see the announcement:

https://bitsharestalk.org/index.php/topic,24937.0.html

@svk created a witness explorer in BitShares 0.X and it included feed frequency as one of the important metrics. I bet all feeds are produced on a cron schedule or some regular timer so frequency is an important metric for feeds, especially in volatile markets.

You are doing a marvelous job BTW, refining your tool, interacting with users to gain important feedback etc. Great customer interaction!

Quote from: Customminer on May 08, 2017, 04:44:22 PM
RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)

I could also start calculating variance difference for every publication. However variance is a subjective thing: A witness can post a high variance pricefeed because the markets are suddenly moving into a new direction and others have not yet responded with new price feeds, so the median is still reflecting the 'old' market and will gradually change when new pricefeeds come available. Average variance over a rolling time will therefore be all in the same range I think.

Yes I can add the 'publishing frequency' as I log all unique pricefeed entries. Feed frequency could be interesting, but can be a subjective indicator as well, misleading. One witness cannot update pricefeeds as long as markets are not volatile and stable without many changes... Pricefeeds are based on feeds published with 24h window, and if markets are not changing, there is no need to publish new feeds and therefore this influences the average pricefeed publication frequency number. So there are not really conclusions to draw from...

Thanks for your feedback @Customminer and please take a minute to check out the recent GUI changes of the tool.

Quote from: Customminer on May 08, 2017, 04:44:22 PM
RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)

@lafona is working on that here: https://lafona.net/witness-stats/

RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)

Made a little witness server report tool, to keep an eye on your disk-space, ram usage & cpu usage and get a report as often as you like (via cronjob), see ann at https://bitsharestalk.org/index.php/topic,24105.msg305715.html

Hi Sakhan, that page is just a viewer for the datafile which is being created and stored here: http://s3.amazonaws.com/roelandp-nl/witnesslog.json every 15 minutes. The source for the logger is a mysql database in which I store the assets and basically the results from the other script I wrote, but then for all witnesses. IMHO a block explorer would require a different set of logging also logging different calls and update on each block. The code for the Bitshares Witness Log logger into mysql is not really worth publishing as I am still learning python :P

Quote from: roelandp on May 07, 2017, 10:14:29 PM

Quote from: sahkan on May 07, 2017, 10:11:43 PM
You are such a great witness! No wonder I voted for you  :D

I was thinking that maybe over time we can morph it into a BTS block explorer....

:D thank you! but https://cryptofresh.com ?

It's not open source. I also meant this: http://roelandp.nl/bitshareswitnesslog/ for an open source

Quote from: sahkan on May 07, 2017, 10:11:43 PM
You are such a great witness! No wonder I voted for you  :D

I was thinking that maybe over time we can morph it into a BTS block explorer....

:D thank you! but https://cryptofresh.com ?

Quote from: roelandp on May 07, 2017, 10:04:20 PM

Quote from: sahkan on May 07, 2017, 07:45:04 PM

Quote from: roelandp on April 24, 2017, 08:40:30 PM
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html

Would you be willing to make this open source?

It was already as announced in the post you link to in your quote :P
https://github.com/roelandp/Bitshares-Witness-Monitor

You are such a great witness! No wonder I voted for you  :D

I was thinking that maybe over time we can morph it into a BTS block explorer....

Quote from: sahkan on May 07, 2017, 07:45:04 PM

Quote from: roelandp on April 24, 2017, 08:40:30 PM
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html

Would you be willing to make this open source?

It was already as announced in the post you link to in your quote :P
https://github.com/roelandp/Bitshares-Witness-Monitor