• Craig
  1. Omniwallet status
  2. Press releases
  3. Identity
• Adam
  1. Omniwallet
     1. Continuing to handle support
     2. About done on staging updates/fixes
        1. Need feedback from ALL on anything out of ordinary
        2. Preparing for soft launch
• Patrick
  1. Finalizing on press – opening salvo in the PR fireworks set-off on bitcoin.com
  2. Finishing tutorials, really happy with Joeri’s tutorial
  3. Catching up on accounting
  4. Recruiting added Dev for dFutures development
  5. Spoke about Omni Layer and Bond at the Botswana Bitcoin Conference
• Marv
  1. Omniwallet
     1. User support
     2. OmniDex testing, UI design w/ Adam
  2. Omniexplorer
     1. A few feature requests
• dexx
  1. Releated Omni Core 0.0.11.2:
     https://github.com/OmniLayer/omnicore/releases/tag/v0.0.11.2
  2. Updated download section:
     http://www.omnilayer.org/download.html#download
  3. Updated OmniJ Travis CI configuration to use latest release:
     https://github.com/OmniLayer/OmniJ/pull/136
  4. Picked latest changes into 0.13 branch and rebased on top of 0.13.1:
     https://github.com/dexX7/bitcoin/tree/13-merged
• Zathras
  1. OmniExplorer:
     1. Fixed ‘Chest outage due to running out of disk space (monitoring covers OE instead now)
     2. Fixed crash caused re-org protection code (missing schema update in reorg code after all pairs)
     3. Redirect going in during coming days, more verification of API usage & then switchover
  2. OmniCore:
     1. Modelled URL payload sizes against Class C & Class D for Craig
     2. Further work on Class D, also ruled out compressing strings – testing with boost & zlib, minimal benefit
     3. Added consensus hash for block 440,000 (https://github.com/zathras-crypto/omnicore/commit/aee37d85579acd42440bc0e4bfe9ad899b12ade8)
     4. Added seed blocks for blocks 430,000 to 440,000 (https://github.com/zathras-crypto/omnicore/commit/5e23d2246625174d67c3d0838699de6991f67d4c)
     5. Debugging slow initialization & parsing speeds
• Sean
  1. Updated website download page for 0.0.11.2
  2. OmniJ Travis CI now running against 0.0.11.2 (merged PR from dexx)
• Judith
  1. Ongoing Communication with projects
  2. Preparing for Hackathon

State of the Layer: All Hands – Nov 22 2016

• Craig
  1. Sponsorship update (CoreTech)
  2. Experimental financial products
  3. Omniwallet status
  4. Litecoin client
  5. Press releases
  6. Identity
• Adam
  1. Omniwallet
     1. Continuing to handle support
     2. Continuing to work on staging updates/fixes
        1. Only major bug left is chart display
        2. Need feedback from everyone to ensure no other bugs/stopping points
• Patrick
  1. Multisig Tutorial
  2. Important Business Development – 3 really good projects
  3. Work on OmniArb.js
  4. Preparing affiliate marketing efforts for Omni assets
• Marv
  1. Omniwallet
     1. User support
     2. OmniDex testing, UI design w/ Adam
  2. Omniexplorer
     1. A few feature requests, bug reports
• dexx
  1. Tagged, built and released Omni Core v0.0.11.2:
     https://github.com/OmniLayer/omnicore/releases/tag/v0.0.11.2
  2. Will publish 0.13 port with latest additions and rebased on top of 0.13.1 soon
• Zathras
  1. Omni Core:
     1. Submitted PR to change the number of signatories for emergency deactivations to 3 (https://github.com/OmniLayer/omnicore/pull/432)
     2. Generated binaries via Gitian for 0.0.11.2 (https://github.com/OmniLayer/gitian.sigs/pull/38)
     3. Ongoing work on Class D (variable length integers) for smaller transactions
  2. Omni Explorer:
     1. Fixed some ‘could not reliably determine trade status’ errors for trades before All-Pairs went live
     2. Fixed new engine crash bug on unconfirmed trades in mempool
     3. Added breakdown of token reserved balances when looking up addresses (feature request from @marv)
     4. Upgraded daemon to Omni Core 0.0.11.2
     5. Back-ported old MasterChest RequestStat API to OE for backwards compat when Omnichest.info domain redirected to OE IP next week
• Sean
  1. OmniJ 0.5.0 released (turned out to be a bit more work than expected)
  2. Working on OLEs today.
• Judith
  1. Ongoing Communication with projects
  2. Preparing for Hackathon

State of the Layer: All Hands – Nov 15 2016

• Adam
  1. Omniwallet
     1. Continuing to handle support
     2. Continuing to work on staging updates/fixes
• Patrick
  1. Omniwallet testing/tickets
  2. In a historic week of chaotic global consciousness, tapped into meme-machine to produce 4 excellent press pieces, two for Bitcoin press, two for mainstream, and we’re talking top-tier mainstream outlets. It’s gonna be lit.
  3. Working on multisig tutorial based on revised RPCs
  4. Testnet activation for cross-property STO and fees to run my scripts and gen the data we need to confidently sign off on activating those.
• Marv
  1. Omniwallet
     1. User support
     2. OmniDex testing, UI design w/ Adam
• dexx
  1. Ported remaining unit tests and raw transaction API for 0.13 port – it’s basically feature complete
  2. Reviewed and merged fee system fix from Zathras for 0.0.11.2
  3. Hardcoded activations for all recent features on testnet for 0.0.11.2 – it’s ready for new tag + binaries
• Zathras
  1. OmniChest.info
     1. Fixed sender/receiver transposed on DEx v1 purchase (thanks Marv)
     2. Fixed server error when trade is invalid (thanks Adam/Marv)
     3. Fixed server error when trade is unconfirmed (thanks Patrick)
     4. Fixed missed trade matches when tradee is filled immediately
     5. Fixed display bug showing 100% sold for invalid trades
     6. Clarified some wording
  2. Omni Core
     1. Submitted Safe mode code (Feature Deactivation) https://github.com/OmniLayer/omnicore/pull/429
• Sean
  1. OmniJ 0.5.0 later today (removing support for Omni Core pre 0.0.11.1)
  2. Draft OLEs coming tomorrow
     1. OLE-001 Omni Layer Enhancements Overview
     2. OLE-002 Omni Layer Enhancements Process (based on BIP process)
  3. General support and advising

State of the Layer: All Hands – Nov 8 2016

• Craig
  1. DEx activation
     1. OmniWallet readiness
• Adam
  1. Omniwallet
     1. Continuing to handle support
     2. Continuing to work on staging updates/fixes
• Patrick
  1. Multiple articles for press placements
  2. Polishing www.blockchainyield.com
  3. Lost some days to bureaucracy
  4. Finishing up tutorials
  5. Calls with promising new issuers – need to review strategy with multisig
  6. Scripting work to test fees on testnet, need proper activation on testnet to employ the script
• Marv
  1. Omniwallet
     1. User support
     2. OmniDex testing
• dexx
  1. Updated version and release notes to prepare Omni Core v0.0.11.2
  2. Tagged, built and verified Omni Core v0.0.11.2:
     https://github.com/OmniLayer/omnicore/releases/tag/v0.0.11.2
  3. Automated testing of 0.13 port is green, the port is 95 % complete:
     https://travis-ci.org/dexX7/bitcoin/builds/174320773
  4. Discussed the way forward for fee system with zathras
• Zathras
  1. General:
     1. Resolved out of space issue on partner Omni Core instance
     2. Renewed OmniChest.info domain name for another year, will redirect to OmniExplorer.info
     3. General discussion various topics (fees/MDEx) / transaction testing
  2. Omni Core:
     1. Ran Gitian build process to generate binaries for 0.0.11.2 (https://github.com/OmniLayer/gitian.sigs/pull/36)
     2. Fixed several bugs with the fee system (https://github.com/OmniLayer/omnicore/pull/426 – thanks dexx7!)
     3. Looking at crash recovery – simulating segfaults issue seems to be with SP watermark rollback, investigating further
     4. Testing variable ints, have a prototype encoder/decoder.  Using existing main ecosystem payloads to test with:
        1. Total history of 107,610 Simple Send transaction payloads.  If sent:
           1. Using standard Class C Payloads: 1,721,776 bytes
           2. Using Compressed Class D Payloads: 731,172 bytes
           3. Savings:  990,604 bytes (42.47% of standard size / 57.53% reduction)
        2. Total history of 816 Trade transaction payloads.  If sent:
           1. Using standard Class C Payloads: 22,876 bytes
           2. Using Compressed Class D Payloads: 14,668 bytes
           3. Savings:  8,208 bytes (64.12% of standard size / 35.88% reduction)
     5. Ported old stale Auditor branch to 0.0.11.2 and fixed up the bugs introduced by the port (https://github.com/OmniLayer/omnicore/pull/427)
     6. Investigating possibility of a safe-mode
• Sean
  1. bitcoinj-addons 0.2.1 released (RPC client now tested and working on Android)
  2. Namecoin SPV lookup beta released that uses bitcoinj-addons
  3. OmniJ
     1. More changes for Bitcoin 0.13 port of Omni Core
     2. Migration from _MP to omni_ method names (Issue #121)
• Judith
  1. Ongoing Communication with projects
  2. Preparing for Hackathon

State of the Layer: All Hands – Nov 1 2016

• Craig
  1. DEx activation countdown
     1. Getting some press
  2. UIT re-hash
  3. Omniwallet UI
     1. Tomas made intro to new developer
  4. Jaxx team integration
  5. 0.13 porting status
• Adam
  1. Omniwallet
     1. Continuing to handle support
     2. Continuing to work on staging updates/fixes
• Patrick
  1. Content revision on press release, reaching out to journalists
  2. Launched http://www.blockchainyield.com and BOND token
  3. Preparing to go 24/7 live with trading systems
  4. Fees testing prep
• Marv
  1. Omniwallet
     1. User support
     2. OmniDex testing
• Zathras
  1. General support & discussion
  2. Submitted PR for QT UI port with new bare MetaDEx UI to dexx’s 0.13 branch (https://github.com/dexX7/bitcoin/pull/5)
  3. Started looking at crash recovery (crashes are part of development & trying things out, but reparses waste a lot of time)
• Sean
  1. Business and personal travel last week
  2. Back to Omni work this week
     1. OLE-001
     2. Updates to bitcoinj-addons, OmniJ, OmniPortfolio
  3. Have some questions about issuance scripts, looking for help.
• Judith
  • Ongoing Communication with projects
  • Preparing for Hackathon

State of the Layer: All Hands – Oct 25 2016