State of the Layer: All Hands – July 28 2015

  • Craig
    1. Board meeting to discuss a number of open items
      1. we still need a “foundation owned” P2SH address which the foundation can use to sign messages to activate features
    2. Feature activation messages
    3. Omnicore build feedback
    4. Multisig RPC utility (using Joshsoccer9’s use case)
    5. Publishing the Omni Core testing guide to subreddit and blog
      1. https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/doc/metadextestingguide.md
  • Adam
    1. Omniwallet
      1. Continuing to handling support / monitor updates from last week
      2. staging login fixed
  • Marv
    1. Omnicore-Qt
      1. several failed attempts to initialize on OSX 10.10.4 latest: https://github.com/OmniLayer/omnicore/issues/151
    2. Omniwallet
      1. found staging login problem
  • Patrick
    1. Moving forward with Sierra Leone survey
    2. Updated model of Omni valuation with a Foundation-backed MM fund
    3. Created some requirement documents for MSC Board to lay out bounties
    4. Will be speaking at Payments Latin America again in Miami on the 24th/25th, highlighting Tether, Factom, dBanking w/ Omni and other tools to bank execs
  • Sean
    1. Continue to be focused on consulting projects
    2. Working on Omni transaction signing in OmniJ (Issue #78, PR #86, etc)
  • Zathras
    1. New consensus hashing system implemented & merged
    2. New checkpointing system implemented & merged
    3. Seed block filtering system finalized & merged
    4. New Preview builds with latest fixes and testnet restrictions fixed uploaded
    5. Initial MetaDEx guide published
    6. Further Omnichest.info work towards v6
    7. Further Omnichest.info API additions for JSON support of tx retrieval

Previous State of the Layer Post: July 21 2015

State of the Layer: All Hands – July 28 2015

State of the Layer: All Hands – July 21 2015

  • Craig
    1. 0.0.9.99-dev has been shared with the team for testing, report issues to: https://github.com/OmniLayer/omnicore/issues
      1. any major issues to discuss?
    2. TMSC consensus issue (raised by Sean): https://github.com/OmniLayer/omnicore/issues/134
      1. issue has been closed, as the consensus issue was to be expected, is now ignored
    3. we need a “foundation owned” P2SH address which the foundation can use to sign messages to activate features
      1. each foundation board member perhaps each has one key for the multisig (should Exodus be one of these?)
      2. also, who has access to sign the builds for distribution?
  • Adam
    1. Omniwallet
      1. Continuing to handling support / monitor updates from last week
    2. github
      1. private repos cleaned up
      2. plan downgraded to free
    3. Announcements mailing list
      1. announcement sent last week about omnicore 0.0.9.2
    4. Continuing cleanup of internal services
  • Patrick
    1. Experimenting with instancing websocket servers to propagate trade data
    2. First round of bounty requirements
    3. Almost ready to integrate Omnicore
  • Sean
    1. Focused on consulting projects last week
  • Zathras
    1. Further work on feature activation by message for Omni Core
    2. OmniChest v6 development for MetaDEx and v0.0.10 features
    3. Minor bugfixes for Omni Core

Previous State of the Layer Post:

July 14 2015

State of the Layer: All Hands – July 21 2015

State of the Layer: All Hands – July 14 2015

Previous State of the Layer Post:

July 07 2015

State of the Layer: All Hands – July 14 2015

State of the Layer: All Hands – July 07 2015

  • Adam
    1. Reviewing private repos on github/mastercoin-msc
    2. Continuing to handle omni support
  • Marv
    1. Yellowfin BI trial – initially using Omniwallet staging db
    2. Sococo Early Adopter Program – which day this week to start?
  • Sean
    1. OmniJ
      1. CurrencyID class simplified, further changes under consideration
      2. Updated to latest bitcoinj-core-0.13-SNAPSHOT
      3. All integration tests are running reliably now – “blue balls” (with occasional false positives due to blockheight mismatches in consensus test)
      4. Test jobs & scripts updated for Omni Core binary named `omnicored`
      5. Code cleanup, etc.
    2. Spec
      1. 1st pass rebrand changes merged (and touched up)
      2. Opened Issue #312 for Token rebrand discussion
    3. Other
      1. Studying naming issues, looking at okTurtles
  • Zathras
    1. Analysis of the BIP66 forks (there have been 2 now, a 6 block and a 3 block fork) due to SPV mining, Omni Core 0.0.9.2 has been released based on 0.9.5
    2. RPC consolidation and standardization merged, all calls are now standardized on “omni_rpccall” and all old “rpccall_MP” calls are aliased and hidden for backwards compatibility.  DexX has also updated and standardized all the help text.
    3. Assisted DexX with rebranding bitcoin to Omni Core & provided icons/imaging etc for installers
    4. Several UI bugfixes merged in including a couple of critical issues related to incorrect data display in the MetaDEx
    5. Last major (3,000 line changes) MetaDEx RPC branch merged which adds and finalizes trade history calls for MetaDEx and moves all the RPC population functions into the new populator and fixes numerous issues
    6. Some proof of concept code written for the new feature activation by message features – note @Craig we need a “foundation owned” P2SH address which the foundation can use to sign messages to activate features – suggest each foundation board member perhaps each has one key for the multisig.

Previous State of the Layer Posts:

June 30 2015
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

State of the Layer: All Hands – July 07 2015

State of the Layer: All Hands – June 30 2015

  • 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

State of the Layer: All Hands – June 30 2015

State of the Layer: All Hands – June 23 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

State of the Layer: All Hands – June 23 2015

State of the Layer: All Hands – June 16 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

State of the Layer: All Hands – June 16 2015