1. Craig
   1. Traveling
2. Zathras
   1. Omni Explorer:
      1. Fixed a bug with reorg protection that allowed a transaction to be entered twice in the database if the reorg occurred while the engine was not in sleep mode (eg while it was actively parsing)
      2. Updated the engine to improve handling of pending transactions (a new cache for transactions that are not yet in a block avoids burning compute resources by repeatedly reprocessing pending transactions over and over)
      3. Updated the engine to add additional locks & an extra temp table to hold processed blocks (avoids race condition that in rare circumstances may allow the API to return an apparently empty block when there are in fact Omni transactions in it)
   2. Omni Core:
      1. Fixed a number of bugs in the QT UI for v0.2 (https://github.com/OmniLayer/omnicore/pull/471)
      2. Reviewed dexx’s PR for hardcoding activation heights (https://github.com/OmniLayer/omnicore/pull/470)
3. Dexx
   1. Reviewed Class D pull request:
      https://github.com/OmniLayer/omnicore/pull/469
   2. Reviewed final pieces for the Qt UI:
      https://github.com/OmniLayer/omnicore/pull/471
   3. Hardcoded activations up to block 438500:
      https://github.com/OmniLayer/omnicore/pull/470
   4. Locked fetching and processing inputs while parsing:
      https://github.com/OmniLayer/omnicore/pull/472
   5. Removed sigops workaround for wallet transactions:
      https://github.com/OmniLayer/omnicore/pull/473
   6. Finalized Omni Core 0.2 release notes:
      https://github.com/OmniLayer/omnicore/pull/461
   7. Created tutorial for creating raw Omni sends:
      https://gist.github.com/dexX7/352670c990ebf9ea31d6346a1519eb52
4. Adam
   1. Omniwallet
      1. Handling support
      2. Looking into multisig/hardware wallets support
      3. Looking at manage issuance/management
5. Sean
   1. Bitcoinj-addons
      1. v0.2.3 released (CHANGELOG)
      2. Started work on v0.2.4-SNAPSHOT
   2. OmniJ
      1. v0.5.1 released (CHANGELOG)
      2. Started work on v0.5.2-SNAPSHOT
   3. OmniPortfolio
      1. 0.1.2-rc-1 released (privately, on Slack)
      2. Waiting for Omniwallet Bitcoin balance fetching improvements for 0.1.2 final release
      3. Ongoing improvements

State of the Layer: All Hands – May 23 2017

1. Craig
   1. Consensus Conference
2. Zathras
   1. Omni Explorer:
      1. Added unique tokens capabilities to a new development instance tracking UIT only
      2. Performance issues, substantial increases in usage, working on upgrades and optimizations
      3. Continuing work on Omni Explorer v8
   2. Omni Core:
      1. Minor improvements to next feature prototypes
3. Adam
   1. Omniwallet
      1. Handling support
      2. Added new v2 address query for sean
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
4. Sean
   1. Bitcoinj-addons v0.2.3 released
   2. OmniJ v0.5.1 ready for release
   3. OmniPortfolio v0.1.2 will be released when “multi-address balance query” goes live on Omniwallet
5. Marv
   1. Omniwallet
      1. User support

State of the Layer: All Hands – May 16 2017

• Craig
  1. Tether arbs with taiwan customers has restored the price back to the peg
  2. Travel
     1. Will be in NY next week for Consensus / TokenSummit
     2. Will be in Israel the following two weeks for d10e, meeting with potential sponsors & partners
  3. Omni Core 0.2 status?
  4. Deloitte proposal?
  5. Protocol enhancement usage
     1. Uniquely Identifiable Tokens
        1. Getting a build of Omniwallet that supports digital objects
        2. Will be testing the prototype with specific use cases
     2. Core.ID / meta-data / address tagging
        1. Will be working with coretech devs on protocol integration
  6. Omnilayer.org redesign and content
     1. Will be engaging a designer
     2. We need to prep how-to’s, walkthroughs and descriptions
  7. Litecoin private release
     1. Emails to alpha@omni.foundation has provided some feedback
  8. Integrators
     1. Made inquires about 0.0.12 update status
     2. Still need feedback from other large integrators
        1. Who else do we need?
• Zathras
  1. Omni Explorer:
     1. Further patched Omni Engine to tolerate pending bug with unreleased 0.2.  Confirmed success (26 occurrences of bug, zero failures)
     2. Rewrote Omni Engine’s supporting library (DLL) to have a much larger debugging footprint in an effort to get more granular troubleshooting data
     3. Started work on Omni Explorer v8 (based on various user feedback over the last year & with a focus on multiple blockchain support)
  2. Omni Core:
     1. Updated Class D pull request based on feedback (thanks to @dexx7)
     2. Continuing the ongoing work on next features to support integrators (class D, central fees, sendmany etc)
• Adam
  1. Omniwallet
     1. Handling support
     2. Worked with marv to improve db queries and speed up wallet load time
     3. Looking into multisig/hardware wallets support
     4. Looking at manage issuance/management
• Sean
  1. bitcoinj-addons v0.2.3 due later this week
     1. Dependency updates only (some are important)
  2. OmniJ v0.5.1 due later this week
     1. Dependency updates
     2. Bug fixes and ecosystem compatibility updates
     3. Omniwallet REST client improvements (for OmniPortfolio, etc)
  3. OmniPortfolio v0.1.2 due next week
     1. Dependency updates
     2. Omniwallet balance query performance improvement
• Patrick
  1. Assessing a new opportunity that would bring resources to the platform

State of the Layer: All Hands – May 09 2017

• Zathras
  1. Omni Explorer:
     1. Recovered several brief outages caused by pending bug in Omni Core 0.1.99, getting more frequent as more transactions are pending
     2. Omni Engine has been patched to attempt to tolerate recurrences of above bug, in testing now
  2. Omni Core:
     1. Attempting to diagnose 500 error from RPC server when querying pending transactions (roughly one occurrence per 50,000 requests)
     2. Submitted minor PR for a fix on change issuer RPC (https://github.com/OmniLayer/omnicore/pull/468)
     3. Submitted PR for prototype of a new transaction class (D) with compressed payloads (https://github.com/OmniLayer/omnicore/pull/469)
     4. Continuing to work on next features to support integrators (class D, central fees, sendmany etc)
• Adam
  1. Omniwallet
     1. Handling support
     2. Pushed additional websocket patches for balance data and improvements
     3. Looking into multisig/hardware wallets support
     4. Looking at manage issuance/management
• Patrick
  1. Expanded Deloitte Proposal – focusing on identity verifiers, contingent tx oracle roles, use cases that can be prototyped as app-level functionalities using RPC
  2. Airbitz Integration
  3. Sphere Crowdsale

State of the Layer: All Hands – May 02 2017

• Zathras
  1. Omni Explorer:
     1. Minor API changes (custom request)
     2. Synchronized dev & prod instances
  2. Omni Core:
     1. Continuing to work on next features including:
        1. Class D
        2. Central Fees
        3. SendMany
  3. General:
     1. Further discussion on central support avenue for Omni users
• Adam
  1. Omniwallet
     1. Handling support
     2. Pushed additional websocket patches for balance data and improvements
     3. Looking into multisig/hardware wallets support
     4. Looking at manage issuance/management
• Sean
  1. Bitcoinj-addons 0.2.2 released
  2. TLS (SSL) issues in consensus tests to Omniwallet CloudFlare are resolved
• Patrick
  1. Pending response from Armenian CB, new website, AML/KYC backend
  2. Plan for budget and dev cycle for BTC->Token trading
  3. Scheduling business development/R&D for TradeLayer fast trading

State of the Layer: All Hands – Apr 25 2017