• Adam
  1. Omniwallet
     1. Handling support
     2. Starting to look into multisig/hardware wallets support
• Patrick
  1. OmniArb Progress –  packaging into NPM/Github repo
  2. OmniArb Features – investigating way to detect 0-confirmation potential trade matches and lock in an arb quickly
  3. BOND to be listed as regulated fund in Armenia on NASDAQ OMX, working on Blockchain Yield Index methodology
  4. Preparing proposal to stock transfer agency for sponsorship/KYC address project
• Sean
  1. Consulting, Android development
• dexx
  1. Omni Core 0.0.11.3 can be released, after “Bump version to Omni Core 0.0.11.3-rel” is merged:
     https://github.com/OmniLayer/omnicore/pull/455
  2. Omni Core 0.2 (based on Bitcoin Core 0.13.2) can be released, after “Update release notes for Omni Core 0.2” is resolved:
     https://github.com/OmniLayer/omnicore/issues/444
• Zathras
  1. Omni Core:
     1. Looking at requirements and options for address tagging
     2. Built prototype for atomic metadata
  2. Omni Core Lite:
     1. Fixed Linux Gitian builds, now working on Windows
     2. Added functionality for remaining transactions to send tab
  3. General:
     1. Usual support & enquiries
• Marv
  1. Omniwallet
     1. User support
• Judith
  1. On going communications with projects

State of the Layer: All Hands – Feb 14 2017

• Craig
  1. Status for Omni LItecoin screenshots and port / repo
  2. Lightning network exploration / output-based conversions
     1. Open letter for meta-protocols
     2. Investigation on protocol feasibility
  3. DEx tutorial / volume and automation
  4. Report on transaction volumes
     1. Tracking usage and relevant stats on omniexplorer
     2. Move to production
  5. Adding Dex transactions to Coinmarketcap
  6. Core.ID discussion / protocol needs
  7. Exodus wallet integration updates
• Adam
  1. Traveling
• Patrick
  1. Made a lot of progress on OmniArb, getting ready to publish to GitHub and make an npm package next week
  2. BOND advertising campaign about to begin, refactored email code
  3. Great market action lately
  4. Preparing blog post on using OmniArb
  5. Resolved RPC issue with command line binding of config
• Sean
  1. Consulting, Android development
• dexx
  1. Merged zathras’ submission “Provide easy access to specific consensus hashes when parsing”:
     https://github.com/OmniLayer/omnicore/pull/456
  2. Omni Core 0.0.11.3 can be released, after “Bump version to Omni Core 0.0.11.3-rel” is merged:
     https://github.com/OmniLayer/omnicore/pull/455
  3. Omni Core 0.2 (based on Bitcoin Core 0.13.2) can be released, after “Update release notes for Omni Core 0.2” is resolved:
     https://github.com/OmniLayer/omnicore/issues/444
• Zathras
  1. Omni Core:
     1. Updated consensus hash PR & configuration doc
     2. Started playing with a few ideas for address tagging
  2. Omni Explorer:
     1. Fixed new hash mismatch bug which prevented engine sleeping and caused database refreshes every 30 seconds
     2. Added URL detection with banner and link to OE when user uses an old OmniChest.info URL
     3. Split out utilization graphs into seperate pages and moved into production
     4. Continuing work to add Send-All support, engine now populating DB with tx & the subsends, now working front end
  3. General:
     1. Fleshing out details for address tagging with @dexx/@craig
• Marv
  1. Omniwallet
     1. User support
• Judith
  1. Hackathon on March 3-4/20107 – http://hack.bitembassy.org/register.html
  2. On going communications with projects

State of the Layer: All Hands – Feb 7 2017

1. Craig
   1. Status for Omni LItecoin screenshots and port / repo
   2. Lightning network exploration / output-based conversions
      1. Open letter for meta-protocols
      2. Investigation on protocol feasibility
   3. DEx tutorial / volume and automation
   4. Report on transaction volumes
      1. Tracking usage and relevant stats on omniexplorer
      2. Move to production
   5. Adding Dex transactions to Coinmarketcap
   6. Core.ID discussion / protocol needs
   7. Exodus wallet integration updates
2. Adam
   1. Traveling
   2. Omniwallet
      1. Handling support
      2. Starting to look into multisig/hardware wallets support
         1. Dev kit received
3. Patrick
   1. Troubleshooting RPC issue
   2. Preparing for 2 major crowdsale offerings
4. Sean
   1. Lightning Network conference call
   2. Consulting, Android development
5. dexx
   1. Reviewed and tested Zathras’ submissions:
      1. Add seed blocks for 440,000 to 450,000 (merged)
      2. Add checkpoint for block 450,000 (merged)
      3. Provide easy access to specific consensus hashes when parsing (waiting for final tweaks)
   2. Finalizing parts for 0.0.11.3 (based on Bitcoin Core 0.10) and 0.2 (based on Bitcoin Core 0.13) releases:
      1. Need an update on DEx1 locking issue
      2. Release notes are last part missing before tagging the releases
6. Zathras
   1. Omni Explorer:
      1. Fixed a bug causing incorrect display of DEx v1 sell offer pricing
      2. Further performance related schema work (migrating raw tx data out of primary tables to shrink them)
      3. Added sell linking, pricing, time and purchase data when viewing DEx accepts (thanks for feedback @Marv)
      4. Working on adding support for Send All transactions to the engine and front end in dev (thanks for feedback @Adam)
      5. Need to discuss testing requirements & then arrange time to move dev improvements over to production
   2. Omni Core:
      1. Added option to easily generate a specific consensus hash during parsing (https://github.com/OmniLayer/omnicore/pull/456)
      2. Added seed blocks for 440,000-450,000 (https://github.com/OmniLayer/omnicore/pull/457)
      3. Added checkpoint for block 450,000 (https://github.com/OmniLayer/omnicore/pull/458)
      4. Battle testing of Omni Core 0.2 going well
   3. Omni Core Lite:
      1. Pushed first rough version of “Omni Core Lite” (port to Litecoin – https://github.com/zathras-crypto/omnicore/tree/0.0.0.1-Z-OmniLite)
      2. Added transaction history support to UI
      3. Fixed a number of bugs (https://github.com/zathras-crypto/omnicore/commits/0.0.0.1-Z-OmniLite)
   4. General:
      1. Support requests are mainly around the same issue (confirmation time) – since the answer is usually the same (fees) can we help users self-service these requests?  Eg FAQ?
7. Judith
   • Ongoing Communication with project

State of the Layer: All Hands – Jan 31 2017