To the authors: my comments are intended to be constructive, not inciteful.  Like you, I endeavor for an accurate and concise message detailing the Bitsares X solution.  Unfortunately, I do not feel qualified to draft content on this topic, rather will contribute by asking clarifying questions for your consideration.

 I am reading this piece as Patrick Bryne.  A majority of the content demonstrates the benefits of the Bitshares X platform as a solution to the crypto-share issuance question he presumably seeks.  I feel a disconnect exists in the body of knowledge presented to fully inform the reader of the complete solution. 

I am having a difficult time reconciling the demonstrated need for identity management in the crypto-share paper to the VOTE DAC content. 

it's more of a social problem than technical. Just don't elect delegates that run multiple instances on the same machine.

I am interested to learn how one may evaluate the block generation and/or network propagation data to determine that multiple delegates are producing blocks from a distinct instance.

I feel Keyhotee Founders should receive their .p2p in the genesis block.

Usage:
wallet_delegate_set_slave <delegate> <master_node> <delay> <enable>

Enable or disable block production for delegate following delayed block production on master node

Parameters:
  delegate (string, required): The delegate name to slave for (may use ALL for multiple delegates)
  master_node (string, required): The IP and port number of the master delegate node.  (Format IP:PORT)
  delay (int, optional) {0-10} : The delay in seconds the slave will wait for receipt of block production from master (default 5)
  enabled (bool, optional): true to enable block production, else false (default: true)

Returns:
  void

I'm doing this entirely as a hobby and a pet project at the moment.

Completely respect this statement. 

Are you willing to share you data dictionary describing the information you are currently collecting? 

Respectfully,
Fox

Here to whet your appetite are just some network health stats:

This data visualization is much needed.  Thank you.

Change request: I believe the rounds are 101 blocks each (rather than 100). 

Looking to the community to continue their support my highly reliable delegate. 

ID    NAME (* next in line)           APPROVAL       PRODUCED MISSED   RELIABILITY   PAY RATE PAY BALANCE         LAST BLOCK
============================================================================================================================
169   fox                             4.0933895679 % 184      3        98.40 %       100 %    412.46580 BTSX      38461

Thanks in advance!

The most important role the delegate serves is the timely and accurate production of blocks.