Community Action Request: Content for Azure BaaS blog post. 

Background:
I've been in contact with Marley Gray, Director, BizDev & Strategy - Cloud and Enterprise, Microsoft on the on-boarding process for BitShares to Azure BaaS.  We are a pull request approval from being live. 

Request:
First, please review Mr. Marley's previous blog posts to see how other blockchain offerings are being positioned [1].  Then, please provide ideas on what you feel should be included in his upcoming blog post highlighting BitShares.  I have a skeleton contained within the metadata.json and README.md files within the GitHub repository [2].  If you choose to tweet this information, please mention @ryanRfox

Gratitude:
Thanks to all those that have tested the scripts and provided feedback thus far; please offer more. 

[1] https://azure.microsoft.com/en-gb/blog/author/marleyg/
[2] https://github.com/ryanRfox/azure-quickstart-templates/tree/review/bitshares-ubuntu-vm

Great work Ken, et al. Congratulations on your 1.0 Release.

Very excited.

I'll be unable to join live this week, so hope Dan can address the folling in his updates:

Are you willing to offer your vision for BitShares software release management?

The active witnesses are keen to engage CNX in a discussion on the topic of a test/staging environment sitting between the CNX development environment and the production BitShsres network.  How do you envision this dialog taking place?

Do you feel the BitShares 2.0.160216 Release [1] with a hard fork date of 23 FEB remains viable, given feedback from partners (i.e. exchanges) and witnesses on their deployment and testing thereof?

[1] https://github.com/bitshares/bitshares-2/releases/tag/2.0.160216

The OP invites discussion of storing private data within a blockchain, permissions to view this data and modifying those rights thereafter.  The OP is directed at the core technology Graphene and references the Enigma project as a possible model.  This thread has, understandably, morphed to discuss applicable applications within the BitShares blockchain. 

May I ask for some technical guidance from @arhag @bytemaster and others with knowledge to discuss the applicability of the Enigma concepts to Graphene?

Specifically, I'm interested to learn more about the key generation process by a witness set (and secondarily, the long term retention thereof).  In the interest of fail fast, please ignor for the moment the fact that the witness set within Graphene is dymaic, both in composition and quantity over time, rather focus on the (shared?) key generation protocol Graphene may ustilize. 

You need to have a white paper discussing the byzantine tolerance, the possible attack vectors, the mitigation, the game theory etc etc - then you will at least have something to direct people towards.

THIS

I do not feel confident in my ability to pen such a whitepaper. Here are a pair of relevant examples for a community member to use as a template:

Tendermint [1]
Interactive Proof of Stake [2]

[1] http://tendermint.com/docs/tendermint.pdf
[2] http://arxiv.org/abs/1601.00275

I fee the network should return all fees paid by the issuer to register the asset in 1.0 as compensation for the asset being eliminated in the 2.0 implementation. Perhaps a worker can be created to pay (refund) the issuers. This may require a worker proposal per issuer. No action should be required of the issuer, just the committee.

What is possible to remedy this?