Charles,
A conversation with Fuzzy and the BitShares community will be beneficial for all.

Open: Remind us all on the backstory of your involvement with Dan, Stan, et al in the early development of BitShares and your subsequent departure to pursue other interests.

Mid: Based on your involvement with a number of crypto-related projects and research of others, how do you foresee the BitShares 2.0 voting mechanics impacting its project governance relative to other projects utilizing their available tool sets?

Late: Do you foresee 1) an a acedemic journal such as Ledger becoming the predominant initial source of publications in this space, or 2) continue to see self-published open access white papers, or 3) corporate interests taking the innovative works toward more restrictive access/licensing?  Relate to CNX and Graphene if applicable.

Respectfully,
Fox

The Fox witness node is operational.  Thanks in advance for your votes.
get_witness fox
{
  "id": "1.6.2104",
  "witness_account": "1.2.30566",
 

Stan,
I'm quite sure you have thought of this one already, yet will offer it up just the same, as I feel it is near the top of of innovations from Cryptonomex and yields an improved user experience.  I abstracted the problem away from Bitcoin specifically, as wallet security exists for all cryptocurrency systems, then presented two implemented solutions.  Having no knowledge of your presentation content, I offer for consideration: present the problem, a legacy implementation (perhaps it's not Bitcoion) and Graphene's implementation.
Best,
Fox

Problem: Wallet Security
Bitcoin Solution: M:N Signatures (Multisig) [1]
Graphene Soltuion: Dynamic Account Permissions [2] + Transferable Named Accounts [3]

[1] https://en.bitcoin.it/wiki/BIP_0011
[2] https://bitshares.org/technology/dynamic-account-permissions/
[3] https://bitshares.org/technology/transferable-named-accounts/

0.9.3 has some issues?

Source?

BitShares 0.9.3 has been released:  https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3

This release will stop block production on October 13th at 9AM EST and adds new API calls for exporting the wallet for Graphene.   

If delegates do not wish to stop producing blocks at the stated date/time then they need not upgrade.   If you are a seed node then you do not need to upgrade. 

All delegates committed to transitioning from the existing BitShares network to BitShares 2.0 should upgrade their node(s) to 0.9.3, publish their version to the blockchain and be ready to produce 2.0 blocks using the Graphene codebase upon launch 13 OCT 2015. 

Stakeholders should watch each delegate's published versions (both active and stand by) and their statements below, then adjust their votes to support delegates that (will) produce blocks for the network they intend to follow after the announced hard fork time.  An updated list is visible at the bitsharesblocks website [1].

Stakeholders should take care to ensure their wallet client software and that of the third parties they may interface with also follow the chain of your choice after the hard fork.  These choices are yours to evaluate and act upon.  Decentralization welcomes you.

[1] http://bitsharesblocks.com/delegates

init witnesses are down for an upgrade

Very well.

Do you expect a new genesis file will be used with the next testnet? 
If yes, may I request the transfer fees be eliminated and the block interval decreased to 3 seconds to match the anticipated launch parameter?

Is anyone able to speak to an estimated time for launching the next testnet?

Thanks in advance,
Fox

How decentralized do you foresee BTS2 network to be at launch and how quickly do you expect it to move toward decentralized witness nodes? Do you have any goals? Why so?

1. I'm contributing with the following amount of BTS: 5000
2. I'm contributing with the following resources (for testers only):  up to 30 x 2 Core VMs 
3. I'm aiming to contribute following amount of transactions per second (for testers only): 500TPS (in short coordinated bursts)
4. I'm willing to contribute scripts for setting up nodes in Azure.