A market pegged asset' supply is created only as a result of a user "borrowing" it into existence by locking some other asset as collateral (usually BTS).

If you were to create a bitWAVES MPA, you would need to also convince witness nodes to provide a price feed for Waves in order to have a 'fair price' for the Asset.

Read more about MPAs here : http://docs.bitshares.org/bitshares/user/mpa.html

Doesn't need to be solely witnesses, it could be the committee (unlikely you'd get many publishers), or you could manually configure private price feed publishers (any Bitshares accounts, up to 25 for now).

Quote from: Customminer on March 08, 2018, 10:35:04 pm

Would you be interested in publishing price feeds for the Hertz Algorithm Based Asset on the Bitshares DEX? https://bitsharestalk.org/index.php?topic=26013.0

Yes, we are doing research about alt's btsprice script and forks. will add Hertz later.

Cool, AFAIK btsprice is no longer actively maintained - perhaps a community focused repo would be more productive than everyone maintaining their own fork? There's a 750 bitUSD bounty on implementing Hertz in btsprice too

Give me a shout when you're planning to publish hertz feeds & I'll add your witness to the approved price feed publisher list.

Cheers

Quote from: Customminer on March 07, 2018, 09:00:10 pm

Attempting to perform direct JSON requests to these api nodes fails: https://eu.nodes.bitshares.works/

Code: [Select]

11 eof_exception: End Of File
stringstream
    {}
    th_a  sstream.cpp:109 peek

    {"str":""}
    th_a  json.cpp:478 from_string
For the mean time, I'll be removing these nodes from the HUG REST API (only when performing these json requests). Cheers

That is how actually the expected response, nothing broken there. Do you have an example of a node that behaves differently?

Depends on the node, but here's the output from this script: https://github.com/BTS-CM/Bitshares-HUG-REST-API/blob/master/work_in_progress/testing_requests.py

Other online nodes work properly.

./\/\/\.
Not online: https://bitshares.crypto.fans/ws
.\/\/\/.
---
Online: https://bit.btsabc.org/ws
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
---
Online: https://api.bts.blckchnd.com
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
---
Online: https://openledger.hk/ws
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
---
Online: https://bitshares-api.wancloud.io/ws
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
...
Error: https://dex.rnglab.org
HTTPSConnectionPool(host='dex.rnglab.org', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))
...
./\/\/\.
Not online: https://dexnode.net/ws
.\/\/\/.
---
Online: https://kc-us-dex.xeldal.com/ws
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
---
Online: https://la.dexnode.net/ws
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
...
Error: https://eu.nodes.bitshares.works
HTTPSConnectionPool(host='eu.nodes.bitshares.works', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))
...
...
Error: https://us.nodes.bitshares.works
HTTPSConnectionPool(host='us.nodes.bitshares.works', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))
...
...
Error: https://sg.nodes.bitshares.works
HTTPSConnectionPool(host='sg.nodes.bitshares.works', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))
...

---

Update: Added 'verify=False' to the request and got the expected output with warnings:

/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
---
Online: https://eu.nodes.bitshares.works
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
---
Online: https://us.nodes.bitshares.works
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===
/lib/python3.6/site-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
---
Online: https://sg.nodes.bitshares.works
<Response [200]>
{"id":1,"jsonrpc":"2.0","result":100}
===

---

So if it's the SSL cert, please update this to A+, B grade seems insufficient: https://www.ssllabs.com/ssltest/analyze.html?d=eu.nodes.bitshares.works

https://certbot.eff.org/ certbot/letsencrypt can provide grade 'A' SSL certs for free.

Attempting to perform direct JSON requests to these api nodes fails: https://eu.nodes.bitshares.works/

11 eof_exception: End Of File
stringstream
    {}
    th_a  sstream.cpp:109 peek

    {"str":""}
    th_a  json.cpp:478 from_string
For the mean time, I'll be removing these nodes from the HUG REST API (only when performing these json requests). Cheers

Hertz is now live on the BTS DEX: https://steemit.com/bitshares/@cm-steem/hertz-is-now-live-on-the-bts-dex

Additional price feed publishers would be massively appreciated - those listed in the OP are pre-approved & can begin supplementing the current price feed producer set at their discretion.

Posted an update with a similar request for publishing price feeds on Steemit last night: https://steemit.com/bitshares/@cm-steem/hertz-updates-28th-feb-2018

Hertz - Oscillating Algorithm Based Asset

Hertz is an MPA which is modified with a sine wave to predictably oscillate with a 14% amplitude, and 28day period, resulting in a price feed range of $0.86 to $1.14.

Price feed scripts have been created for wackou's bts_tools, xeroc's bitshares-pricefeed and the reference Hertz python-bitshares based price feed implementation.

A $750 (bitUSD) bounty is still available for the implementation of Hertz in the btsprice price feed repo.

I'm seeking additional price feed publishers, I've pre-approved 25 price feed publishers (detailed below) who can begin publishing price feeds for Hertz at their discretion. Any elected witnesses not currently publishing price feeds - I'd greatly appreciate feedback regarding what would help you begin publishing price feeds.

Approved price feed publishers:
fox, wackou, xeldal, xman, abc123, xn-delegate, datasecuritynode, delegate.ihashfury, bhuz, delegate-1.lafona, delegate.freedom, elmato, in.abit, verbaltech2, witness.yao, witness.still, roelandp, taconator-witness, blckchnd, sahkan-bitshares, openledger-dc, sc-ol, billbutler-witness, delegate-zhaomu, hertz-feed.

Actively publishing price feeds:
wackou, delegate.ihashfury, verbaltech2, roelandp, taconator-witness, blckchnd, sahkan-bitshares, sc-ol, delegate-1.lafona, hertz-feed.

Not publishing price feeds yet:
fox, xeldal, xman, abc123, xn-delegate, datasecuritynode, bhuz, delegate.freedom, elmato, in.abit, witness.yao, witness.still, openledger-dc, billbutler-witness, delegate-zhaomu

We may need to increase the max price feed publisher quantity again unless I start swapping above approved (and inactive) price feed publishers for willing parties.

Cheers,
CM.

References:
Price feed monitor: https://btsapi.grcnode.co.uk/home
Hertz asset page: http://open-explorer.io/#/assets/HERTZ
Hertz technical documentation: https://sites.google.com/view/hertz-aba/
Wackou's price feed repo: https://github.com/wackou/bts_tools/
Xeroc's price feed repo: https://github.com/xeroc/bitshares-pricefeed/
btsprice bounty: https://github.com/pch957/btsprice/issues/4
Reference repo: https://github.com/BTS-CM/scripts/blob/master/hertz-feed.py

We're not talking about actual history here, just leftover feeds from people who are no longer witnesses.

A history of settlement prices would be interesting, we could add that to ES. But that's a different subject.

Will committee members and private price feed publishers be affected too?

What is the max age of a price feed? Some MPA like XCD (http://open-explorer.io/#/assets/XCD) only need a feed published once per year.