• Craig
  1. Automated DEx trading
  2. Next releases
• Adam
  1. Omniwallet
     1. OmniDex Interface launched
     2. Continuing to handle support and feedback from launch
• Patrick
  1. Trying to test btc spend and fail-safing of Dex trading system
  2. Finishing email automation tool for fulfilling orders of a product through a website (vending machine w/ some KYC)
  3. Final Omniwallet testing last week
  4. Futures contract interviews
  5. Feedback on making Dex phase one open to non-OMNI pairs
  6. Design to automate Dex phase one trading in Omniwallet
• Marv
  1. Omniwallet
     1. OmniDex launch
     2. Monitoring support
  2. OmniExplorer
     1. Reporting bugs & feature requests
• dexx
  1. Fixed Travis CI configuration for 0.13 port
  2. Hosted Mac OS X SDK for Travis CI on AWS S3
  3. Fixed restoring of default minRelayTxFee in unit tests, so random test order also works
  4. Bumped version of 0.13 port version to 0.1.99, and updated related tests
• Zathras
  1. Omni Explorer:
     1. Fixed a crash in MetaDEx market page when the total amount of available tokens overflows an unsigned 32-bit integer (thanks for report Marv!)
     2. Fixed an issue where cancelled trades with no matches would show as 100% sold (thanks for report Marv!)
     3. Working on engine logic problem that results in matched trades being recorded in multiple iterations (causing duplicates) (thanks for report Marv!)
  2. Omni Core:
     1. Working on optimizations, achieved target of sub-10 minute parsing!  Improvements include:
        1. For Class B, only prepare an equivalent number of SHA256 hashes to the packet count (rather than MAX_SHA256_OBFUSCATION_TIMES each transaction)
        2. No longer recalculate fee distribution thresholds every block, only when smart property token counts change (eg grant or issuance)
        3. Skip iterating the vector of checkpoints unless we’re actually in a block that is %10000.
        4. Fix the MAX_SEED_BLOCK const that was causing seed blocks >390K to be ignored
        5. Skip actually fetching a property from the SP database when we need to check if it exists (property ID’s are sequential so existence can be inferred from peeking next available property ID)
        6. Wallet cache improvements
        7. Migrate the tally map from std::map to std::unordered_map (this is actually slower at the beginning when we only have a small number of elements, but by about block 300,000 the hashtable lookup of unordered_map starts to see substantial improvements over std::map).
        8. Don’t bother iterating over the outputs again in HandleExodusPurchase if we’re past the Exodus crowdsale & on mainnet
        9. Added model to drop non-Omni transactions faster by comparing bytes in scriptPubKey looking for marker bytes and only examining interesting transactions more closely
• Sean
  1. OmniPortfolio 0.1.2 coming this week
     1. Update to OmniJ 0.5.0
     2. Use Omniwallet address array balance query (using Omniwallet staging server)
• Judith
  • Ongoing Communication with projects

State of the Layer: All Hands – Nov 22 2016