RE: Hero Rejected by BitShares Committee after a Year in Operation

You are viewing a single comment's thread from:

Hero Rejected by BitShares Committee after a Year in Operation

in bitshares •  6 years ago  (edited)

To be fair, the HERO ABA does have available permissions/flags which have associated centralized risk (transfer back to issuer, whitelist/blacklist, market fees) which was imposed on the Bitshares committee without their full consent (AFAIK - no offence intended).

These risks may not be any worse than any of the existing 'committee owned smartcoins' however it's still additional risk on top of their current responsibilities.

If you don't want responsibility of controlling the HERO ABA then would you consider transfering ownership of the asset to null? Unless there is a necessity for asset owner interaction during global settlement recovery scenarios?

Time to disable the following flags?

  • White list
  • Override authority
  • Transfer restricted
  • Disable force settle
  • Global settle
  • Disable confidential
Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  
  ·  6 years ago (edited)

Of course, the committee is in charge of setting parameters and had full control to set these switches themselves as they saw fit. I'll ask xeroc to set them appropriately.

"null" have owner, the correct account to transfer is "null-account".