• Craig
  1. Memo field on Send status
  2. details on action tracking system
  3. Omni Wallet Desktop release prep:
     1. Release candidate for 0.0.10, end of week
     2. Feature activation testing on testnet – results?
     3. Omni Core testing guide to subreddit and blog:
     4. https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/doc/metadextestingguide.md
     5. 0.0.10 RPC documentation: https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/src/omnicore/doc/rpc-api.md
  4. 0.0.10 release dialogue
     1. https://github.com/OmniLayer/omnicore/issues/194
     2. what items remain?
• Adam
  1. Omniwallet
     1. Continuing to handling support / monitor updates from last week
     2. Updating Omniengine to match omnicore 0.0.10 updates
     3. Tweaked pending tx support to prune after 1 day instead of 7
  2. Working with 3rd party integrators
• Patrick
  1. Refund complete, get bullish.
  2. Did little coding, so back on track with my coding priorities now.
• Marv
  1. curious to understand more about memo field
• Sean
  1. OmniJ
     1. a little support
     2. Waiting for new Omni Chest API for PR #117
  2. Naming/Identity issues
     1. More work on beeLin
     2. Preparing for Rebooting Web of Trust workshop
  3. Looking for consulting work
• Zathras
  1. Working on API connector branch further:
     1. UpdatesDB in place
     2. Updates now queryable via RPC
     3. Development being moved back to GitHub in PR 267
     4. Coverage extended, though still does not cover 100% of state actions
• Dexx
  1. Finalized the raw transaction API to construct Omni transactions as raw transactions, which is useful
     1. to create the feature activation transactions,
     2. it’s the missing piece for multisig/arbitration use-cases,
     3. for more details see: https://github.com/OmniLayer/omnicore/pull/77.
  2. Other than that, mostly on standby and awaiting a release plan.

Previous State of the Layer Post: Oct 20 2015