(Option, instead of being an xml tree, the asset contract can be a Merkle tree of various terms and conditions).

Process:
1.	The ASSET CONTRACT is hashed (or if it is a Merkle root, then it just left as-is).
	a.	Creates: ASSET CONTRACT ID

2.	A set of rules for a P2SH (pay-to-script-hash) address is created; these rules may be as simple as a (x of y) or may be more advanced.

3.	These rules are applied over the ASSET CONTRACT ID
	a.	Creates the SIGNED ASSET CONTRACT

4.	The final P2SH script is then created, with the hash of the SIGNED ASSET CONTRACT included as a constant.
	a.	This creates the P2SH address … that is the ISSUER ASSET ID.

The ISSUER ASSET ID must change if the contract changes.
The ISSUER ASSET ID can be verified by SIGNED ASSET CONTRACT matching the rules in the P2SH.
Any action of the ISSUER ASSET ID is enforced by the entire Bitcoin Network.

Every satoshi that this P2SH outputs equals 1 token for the asset contract defined in it (if everything verifies correctly)!