• Craig
  1. Omni Protocol Spec has been updated and moved to OmniLayer repo
  2. Test builds for 0.0.10?
     1. need to make the angry warning be on first-run only
  3. Test plan for remaining DEx items, new RPC calls.
  4. listtransaction_MP too heavy a call
  5. Discussions surrounding additional meta-data fields, protocol enhancements requested by integrators
  6. Token re-brand – MSC becomes…. OMNI?  Omni MSC?  MSC?
• Adam
  1. Omniwallet SSL cert updated last week
  2. Need to review private repos on github/mastercoin-msc
  3. Continuing to handle omni support
• Marv
  1. Yellowfin BI trial – initially using Omniwallet staging db
  2. Sococo Early Adopter Program?
• Patrick
  1. Laid out Omniwallet API requirements, need tech consensus from Adam/Tomas.
• Sean
  1. We now have a spec that’s titled Omni Protocol Spec
     1. What do we call the Real/Live/Production/MSC Ecosystem?
     2. Are we going to rename the tokens?
  2. OmniJ
     1. Fixed most integration test issues with 0.10/0.0.10, except this one.
        1. Problem caused by unexpected mining rewards showing up on a test address during RegTest
     2. BitcoinClient.waitForServer() upgraded for Bitcoin 0.10+
        1. Handles “Scanning/verifying messages”
     3. Improvements to log messages handling/levels, ongoing (wtih Dexx)
     4. Next up
        1. 0.3 release binaries
        2. Transaction signing improvements for hardware wallets.
  3. Working on Java/bitcoinj-based Bitcoin JSON-RPC server. Stay tuned.
  4. Still interested in naming issues, but back-burner for next few weeks.
• Zathras

1. Primarily work has focused on consolidating all the various branches to move towards a code base to stage a 0.0.10 release candidate on.  Including:
   1. Parsing changes now merged in, this is substantially faster and refactored code primarily courtesy of DexX7 which includes big improvements such as txin caching and class specific parsing.  Legacy code will be used until the next consensus-breaking feature goes live.
   2. UI changes now merged in, this includes a number of bugfixes related to performance and data display and includes a new model to completely re-init the UI in the case of a re-org (previously old data would still be present after orphans/chain reorgs)
   3. RPC changes pending merge, this includes a number of bugfixes and changes suited to MetaDEx RPC.
2. Failure mode for STO receipts discovered and wallet iteration process rewritten to handle the fact that when watch addresses are used, transactions are added to the wallet during a rescan (ie not in chronological order) which skews ordering in history and calls like listtransactions_MP
3. Performance for RPC is substantially improved (again credit to dexx7) – all RPC calls except 2 are now thread safe and can be called at the same time in addition to massive performance improvements due to serialization of SP data
4. Proof of concept code for activating features based on notification messages instead of hard-coded blockheights written – see https://github.com/OmniLayer/omnicore/issues/104
5. Test builds incoming, so much has changed since last test builds that a new set will be created again, will likely form first 0.0.10 release candidate
6. Starting work on installers, binaries, documentation, changelog, release processes etc for 0.0.10

Previous State of the Layer Posts:

June 23 2015
June 16 2015
June 09 2015
June 02 2015
May 26 2015
May 19 2015
May 12 2015
April 28 2015
April 21 2015
April 14 2015
March 31 2015
March 24 2015

• Craig
  1. Ongoing integrations with third-party providers
  2. Additional API support, Omnichest/OmniWallet.org/others
  3. Test builds for 0.0.10 – this week (Windows, OS X)
     1. need to make the angry warning be on first-run only
  4. Test plan for remaining DEx items, new RPC calls.
  5. listtransaction_MP too heavy a call – ways to improve?
  6. incorporating any bitcoind 0.10.x+ features?
  7. Spec moved to OmnLayer repo, needs updating
  8. Discussions surrounding additional meta-data fields, protocol enhancements requested by integrators
• Adam
  1. Service renewals completed this week
  2. Continuing to handle omni support
• Marv
  1. Business Intelligence tools research, e.g. for Omniwallet db data analysis
• Zathras
  1. Ongoing work on UI
     1. many bug fixes still being discovered and being fixed
     2. significant performance improvements
     3. additional transaction hash caching
     4. less freezes and less hangs during processing work
• Sean
  1. Pull request #309 renaming Spec to ‘Omni Protocol’ ready for review/merge.
     1. We should consider renaming Mastercoins to Omnis
     2. We could also use a name for the Mastercoin/Live/Real Ecosystem.
• Patrick
  1. Metaliquid: integrated SQL indexing of JSON for long-term indicators/metrics, refitting for Websockets for speed improvements, trading both spot and futures.
  2. Can start a dBank prototype with tx 54,55,56 scriptings to RPC need documentation

Previous State of the Layer Posts:

June 16 2015
June 09 2015
June 02 2015
May 26 2015
May 19 2015
May 12 2015
April 28 2015
April 21 2015
April 14 2015
March 31 2015
March 24 2015

• Craig
  1. Getting Omni support in multiple multisig providers for backend wallet solutions
  2. Additional API support, Omnichest/OmniWallet.org/others
  3. Test builds for 0.0.10?
• Adam
  1. Working with Craig on service renewals
  2. Continuing to handle omni support
• Zathras
  1. Further UI refinements:
     1. Watch only support improved – watch addresses will no longer trip up the UI, and can be used to view/watch balances but not spend from
     2. Recent transaction support for Omni transactions in overview
        Rewritten signaling for substantial performance improvements (reg test UI runtime down from 8 mins to 3.5 mins)
     3. Improved pending support (now displays icon and tooltip in status bar while outbound transactions are unconfirmed)
     4. Wallet model reliance largely removed
     5. Many bug fixes and minor improvements
• Sean
  1. Continuing OmniJ work
     1. 0.3 release
     2. Experimenting with server-side components
  2. Updating specification to ‘Omni Protocol’ specification: Issue #308
  3. Will open naming issue on Github – done: Issue #310

Previous State of the Layer Posts:

June 09 2015
June 02 2015
May 26 2015
May 19 2015
May 12 2015
April 28 2015
April 21 2015
April 14 2015
March 31 2015
March 24 2015

• Adam
  1. Ongoing omni support
  2. Working with Craig on upcoming service renewals
  3. Github moves for primary repos complete
     1. Spec, Omniwallet, OmniEngine, omni-devops
• Marv
  1. Omni
     1. reviewed replacements for tx21
• Zathras
  1. Dev infrastructure deployed for OSX testing to address raised bugs
  2. Various bug fixes
  3. DexX has introduced the new MetaDEx transactions and these are merged
  4. Continuing work on RPC layer, including deduplicated populator
  5. Expanded MetaDEx class to contain an “amounttofill” field that provides the exact amount needed to “buy out” (ie purchase all available tokens) a trade.  Attribute now exposed in MetaDEx objects in RPC layer
  6. Performance work and evaluation on UI.  Performance testing commits (temporary will be removed) – Currently looking at capping UI display to most recent 1000 transactions or whether to rewrite model usage.
  7. Reviewed some great submissions from @dexx7 for merge
• Sean
  1. Jenkins server rebuild complete: ci.omni.foundation
     1. Java 8, NGINX, SSL, latest Jenkins, etc.
     2. Bitcoin 0.10 blockchain (omnicore-0.0.10)
     3. Problem with consensus tests and “Parsing Omni Layer transactions…” / “Verifying blocks…” JSON status — currently investigating.
     4. New user database, let me know if you need write or admin access.
  2. OmniJ
     1. 0.3 release still in progress (spent all my time on Jenkins)
  3. Thinking about adding basic naming / SSL cert registration to the spec.
• Patrick
  1. Metaliquid: order functions implemented, metrics fully implemented, testing performance

Previous State of the Layer Posts:

June 02 2015
May 26 2015
May 19 2015
May 12 2015
April 28 2015
April 21 2015
April 14 2015
March 31 2015
March 24 2015

• Craig
  1. Attending Exponential Finance Conference
  2. Looking for testnet build Omnicore for general testing
     1. prerelease looks good so far
• Adam
  1. Omni support
     1. working with Craig to update Zendesk
  2. Omniwallet SSL renewal
  3. Revisit moving Github moves.
• Zathras
  1. Continuing work on RPC layer
  2. Expanded MetaDEx class to contain an “amounttofill” field that provides the exact amount needed to “buy out” (ie purchase all available tokens) a trade.  Attribute now exposed in MetaDEx objects in RPC layer
  3. Performance work and evaluation on UI.  Performance testing commits (temporary will be removed) – Currently looking at capping UI display to most recent 1000 transactions or whether to rewrite model usage.
  4. Reviewed some great submissions from @dexx7 for merge
• Sean
  1. Jenkins server rebuild in progress
     1. Java 8, NGINX, SSL, latest Jenkins, etc.
     2. Bitcoin 0.10 blockchain (omnicore-0.0.10)
  2. OmniJ
     1. DexX7 pull requests
     2. 0.3 release to Bintray planned for later today
  3. Move some repos from mastercoin-MSC to OmniLayer Github organization
     1. omni-devops
     2. spec?
  4. SF Bitcoin Devs Meetup: RevokeSSL
     1. Revocable self-signed TLS certificates via Bitcoin blockchain
     2. proof-of-concept Github repo
     3. Has me thinking about naming functions in OmniLayer
• Patrick
  1. Metaliquid: Got ops squared up and all bugs fixed, except one work-around that’s still testing, testing order placements logics and implementing metrics
  2. Now that I’ve got momentum with algo trading will go back and finish editing for the Sierra Leon Tether/Omniwallet video

Previous State of the Layer Posts:

May 26 2015
May 19 2015
May 12 2015
April 28 2015
April 21 2015
April 14 2015
March 31 2015
March 24 2015