Update specification for 0.0.10 changes

[dexX7]

The specification needs to be updated to address the upcoming changes introduced in Omni Core 0.0.10.

While the release notes are not yet finalized, it should provide an overview:

• Data embedding with OP_RETURN
• Updated transaction format of MetaDEx transactions
• Address side effect of granting tokens
• No longer allow DEx "over-offers"
• New "send-all" transaction type
• Don't allow ecosystem crossovers for crowdsales

In the case of DEx "over offers" the specification needs to address both the old rules, as well as the new rules, given that there are unfortunally historical transactions which would be invalid otherwise. As for the other changes, chances are very good that we can just amend the specification in retrospective, or add the missing pieces.

[marvgmail]

Also:

• Is tx type 21 supported?
• Is tx type 56 (revoke tokens) still limited to the address that created the tokens, or can any owner of the tokens revoke those that are owned, and available?

[CraigSellars]

Where do we stand on getting the spec updated?

[zathras-crypto]

I think the spec needs an entire review and some attention/love - there are PRs that are 18 months old.

[ABISprotocol]

Maybe add something (simple) for people who are looking for information about decentralized exchange? Seems a little thin on details when you come to the front page. Note: as launched March 15, 2014 (and described in the wiki), the decentralized exchange “enables peer-to-peer exchange of any cryptocurrency or token with any other cryptocurrency or token." However, the wiki has been offline for a while, and the front page (omnilayer.org) is light on details, especially for any newcomer.