Many updates to the HUG REST API since the original post. Most recently, a Bitshares testnet HUG REST API server was created! https://steemit.com/bitshares/@cm-steem/bitshares-testnet-hug-rest-api-server-now-online

I've been working on getting the HERTZ Algorithm Based Asset live on the Bitshares network recently, and ran into problems providing more than 10 private price feed publisher entities (Rather than witness|committee fed).

Would it be possible for the committee to increase the 'maximum_asset_feed_publishers' value from 10 to say 25?

As far as I'm aware, there's no risk associated with increasing this value, right?

Relevant links:
https://github.com/bitshares/bitshares-ui/issues/1025
https://steemit.com/bitshares/@cm-steem/bitshares-committee-request-increase-the-maximumassetfeedpublishers-value-from-10-to-25
https://steemit.com/bitshares/@cm-steem/hertz-42-activated-4-more-bitshares-witnesses-to-go-more-hertz-related-updates
https://sites.google.com/view/hertz-aba/

Thanks for your time,
CM.

Thank you for the explanation. So, how can I determine for a specific asset if it was completely borrowed into existence or if some of the supply was issued by some centralized individual or organization?

It's a smartcoin, it's fundamentally impossible to centrally issue without backing collateral. It can only be shorted into existence with 200% collateral.

Furthermore, in the BTWTY page (https://wallet.bitshares.org/#/asset/BTWTY) the asset is listed with the permission "ISSUER MAY TRANSFER ASSET BACK TO HIMSELF". So it seems that the individual who controls the issuing account (in this case estefantt) is able to just transfer the assets back to himself as he wishes. Is there a good reason that this permission flag is enabled? It seems that most other assets (HERO, BitUSD, ...) have this flag enabled as well. In the case of BitUSD the issuer is the committee-account, so that I assume that it is much harder to make use of this permission. But in the case of BTWTY and HERO, it seems that it makes the asset completely centralized and controllable by the one individual who is listed as issuer. Am I missing something here as well? Thank you.

The Hertz algorithm based asset has surrendered such permissions, you're right that this is a troubling flag to not have permanently disabled.

I'd support the effort in principle, however with Cryptonomex no longer being "the company behind bitshares" ownership of the domain should be transferred to the BitShares Foundation.

I agree, however the Bitshares Foundation equally doesn't answer directly to BTS holders, right?

I think you need a basic account before creating a premium account, given that it costs extra BTS for the premium account name.

It's a market pegged asset, thus it has decentralized issuance - they're shorted/borrowed into existence.

@roelandp: What price feed script are you using? You're quite far out from the intended price feed value.

I've added a public API for looking up a reference Hertz price feed: https://btsapi.grcnode.co.uk/get_hertz_value?api_key=123abc

Thanks