If you want to see DPOS in action - very very soon…if you want to see working bitAssets -seems like not that soon.

Yes he could. You can already issue assets on the test net.

The pourpose of this article is to teach bitcointalk users about TITAN.
When SATAN meets TITAN
Original Proposal using ECC
Recently, core developer Danial Larimer revealed "Secure Payments to Users by Name". He descripes, based on ellyptic
curve cryptography (ECC), how to generate a unique receiving address for a user.  The scheme works as follows:
 
    Create TempPrivateKey TEMP.PRIVATE_KEY;
    TEMP.PRIVATE_KEY * USER.PUBLIC_KEY  =>  SECRET  =>  ONE_TIME_PRIVATE_KEY  =>  ONE_TIME_ADDRESS
 
The payee can send his transaction that pays to ONE_TIME_ADDRESS and attaches TEMP.PUBLIC_KEY as message to the transaction.
Every client on the network will be able to perform the following operation:
 
USER.PRIVATE_KEY * TEMP.PUBLIC_KEY => SECRET => ONE_TIME_PRIVATE_KEY
 
If   ONE_TIME_PRIVATE_KEY is the one that controls ONE_TIME_ADDRESS  then   user will immediately spend the funds from ONE_TIME_ADDRESS to
a new address because the sender retains the ability to cancel the  transaction.
 
Note: 
turns  out this  crypto technique already existed and was called   "stealth  addresses". The  fact that we re-invented it is good news though!
However  as the DPOS blockchain allowes for adding the TEMP.PUBLIC_KEY as a  comment to the transaction, the receiver does not need to brute-force  test
if a particular transaction can be spent by him. This is the case for stealth-addresses
 
Pros:

    The following features result from his proposal:

    no need to exchange addresses, instead a Name can be given

    ability to encode a message and 'from' data into the transaction for payment details

    the receiver is anonymous to everyone but the sender as for each payment a temporary one-time address is generated

    potential to cancel/retract a transfer if it is not accepted in a timely manner, which is impossible for any other transaction. To prevent chargeback the receiver simply wipes his temporary one-time address

    simplifies accounting in the wallet

    generates higher fees and dividends

 
Cons:

    Daniel also listed the basic drawbacks of his approach which are namly:

    Uses more space in the blockchain

    Requires two transactions

    Results in higher fees

 
Optimized Algorithm
However the first drawback go resolved quickly by the use of hierachical extended public keys.
The basic approach can be seen from Daniels pseudocode:
 
    dan   => DANS_EXT_PUBLIC_KEY
    scott => SCOTTS_EXT_PUBLIC_KEY
   
    scott:  Generate OneTimePrivateKey & OneTimePublicKey Pair
    scott:  OneTimePrivateKey * DANS_EXT_PUBLIC_KEY => SECRET
                DANS_EXT_PUBLIC_KEY.child( SECRET ) => RECEIVE_PUBLIC_KEY => RECEIVE_ADDRESS
    scott:  RECEIVE_PUBLIC_KEY * SCOTTS_EXT_PRIVATE_KEY => CHECK_SECRET
                                                        => SHORT_HASH(CHECK_SECRET) == SHORT_SIGNATURE
    scott-broadcast:   OneTimePublicKey + RECEIVE_ADDRESS + ENCRYPT( from scott + SHORT_SIGNATURE, SECRET )
    dan:   OneTimePublicKey * DANS_EXT_PRIVATE_KEY => SECRET
              DANS_EXT_PRIVATE_KEY.child( SECRET ) => RECEIVE_PRIVATE_KEY =>
                             => RECEIVE_PUBLIC_KEY => RECEIVE_ADDRESS
 
    dan:   DECRYPT( data, SECRET ) => "from scott" + SHORT_SIGNATURE
    dan:   SCOTT_EXT_PUBLIC_KEY * RECEIVE_PRIVATE_KEY => CHECK_SECRET => SHORT_HASH(CHECK_SECRET)
 
This is a variation of stealth addresses (http://www.coindesk.com/stealth-addresses-secret-bitcoin-privacy )   that leverages the
name system to solve the first part of the problem.
 
Thus, the protocol allows to

    Send Anonymously To Any Name => SATAN

    or Transfer Invisibly to Any Name  => TITAN

 
Combining  this with well-known techniques like CoinJoin (darkcoin) or  ring-signatures allowes to completely send and also receive
anonymous transaction
 
Furthermore, these recent updates shed light to the power of Keyhotee as then
the use of name@xts can address individuals or DACs.
 
Mailing Money is within reach!

He and his lawyers need to know about Bitshares.

So every delegate finds the same amount of blocks and gets the same reward as long as he is in the top 100, right?

I've followed the advice of Stan and Toast and produced the following list of balances for AGS
http://pastebin.com/u9WKpcAb

However the process is sketchy and prone to error and interference - this is unacceptable for such important data. It leaves a crypto-asset creator with the responsibility for any errors, but without the power to ensure there are no errors.

Thus, I've posted the list of balances in advance of launch to transfer the responsibility of ensuring they are correct to I3. I3 - please confirm the list of balances is correct.

It occurs to me it would be easier for I3 to create a list of balances and sign them, rather than try to verify that the list that I've produced is correct. It is therefore my recommendation that I3 does that for this and future distributions.