anchor.diff:  
   * Create a hash that represents the state of particular currency at specific block height.
   * Create a hash that represents the state of all currencies at a specific block height.
  -* Create a hash that represents the changes to balances (deltas) that occured during a particular block. (This may be hard to calculate and/or of limited use)
  +* Create a hash that represents the changes to balances (deltas) that occurred during a particular block. (This may be hard to calculate and/or of limited use)
   * Chance of hash collision is astronomically low
  -* Hash data can be stored for every block height value from a trusted implmentation and used to regression test changes to that implementation.
  +* Hash data can be stored for every block height value from a trusted implementation and used to regression test changes to that implementation.
   * Hash data can be used to track an inconsistency to a particular block and currency ID when troubleshooting.
   
   == Proposed Implementation
  
positive.code: 
  === Block Consensus Hash
  
  This is a hash of all consensus data for all currencies in existance at a specific block height.
  
  === Currency Delta Consensus Hash
  
  A hash of only the changes to balances of a specific CurrencyID that occured during the specific block.  This has may not be very useful and/or may be difficult to compute. 
  
  === Block Delta Consensus Hash
  
  A hash of the changes to balances of a all currencies that occured during the specific block.  This has may not be very useful and/or may be difficult to compute. 
  
  == Notes on Hash Algorithms
  
  
negative.code: . It is a well-known algorithm
  . All Bitcoin and Omni Protocol implementations have an implementation available
  
  Because Consensus Hashing is neither used nor required by the specification for determining balances or for validating transactions, it is not strictly necessary to use a cryptographically secure algorithm, nor are there any direct security implications of this proposal.
  
  
  